I am trying to create a "Database Connection" within Ebase to a SQLserver 2008 database running within an instance using the following URL:
jdbc:jtds:sqlserver://sql2008:1433;instanceName=IDOX;DatabaseName=UniformLiveReports;integratedSecurity=true;
however it does not work, do the Ebase database connections support the type of syntax used above, or am I doing something completely wrong?
jdbc to MS sql2008/instance/database
Moderators: Jon, Steve, Ian, Dave
-
- Ebase User
- Posts: 201
- Joined: Fri Dec 20, 2013 1:29 pm
- Location: Dartford Borough Council
- Contact:
-
- Moderator
- Posts: 1342
- Joined: Wed Sep 12, 2007 12:49 pm
Two things:
1. The general format of the connection string is jdbc:jtds:sqlserver://<server_name>/<database_name>;instance=<instance_name>;property1=xxx;, so in your case:
jdbc:jtds:sqlserver://sql2008:1433/UniformLiveReports;instance=IDOX;
I don't think the DatabaseName property is supported by the JTDS driver.
2. Also the integratedSecurity property is not supported by JTDS. If you want to use Windows authentication, you should use the domain property instead and specify a specific Windows user and password - here are more details http://jtds.sourceforge.net/faq.html - see the domain property.
The alternative is to use Sql Server authentication instead of Windows authentication, then you explicitly define a user/password within SQL server and specify these on the connection.
Regards
Jon
1. The general format of the connection string is jdbc:jtds:sqlserver://<server_name>/<database_name>;instance=<instance_name>;property1=xxx;, so in your case:
jdbc:jtds:sqlserver://sql2008:1433/UniformLiveReports;instance=IDOX;
I don't think the DatabaseName property is supported by the JTDS driver.
2. Also the integratedSecurity property is not supported by JTDS. If you want to use Windows authentication, you should use the domain property instead and specify a specific Windows user and password - here are more details http://jtds.sourceforge.net/faq.html - see the domain property.
The alternative is to use Sql Server authentication instead of Windows authentication, then you explicitly define a user/password within SQL server and specify these on the connection.
Regards
Jon
Last edited by Jon on Thu Jul 31, 2014 6:09 am, edited 1 time in total.
0 x
-
- Ebase User
- Posts: 201
- Joined: Fri Dec 20, 2013 1:29 pm
- Location: Dartford Borough Council
- Contact:
MS Drivers
Hi Jon,
Many thanks for the swift reply, if I cannot get the "jtds" driver to work, I will try to deploy the Microsoft JDBC driver into Ebase and hope that this does the job.
Kind regards
Neil
Many thanks for the swift reply, if I cannot get the "jtds" driver to work, I will try to deploy the Microsoft JDBC driver into Ebase and hope that this does the job.
Kind regards
Neil
0 x
-
- Moderator
- Posts: 1342
- Joined: Wed Sep 12, 2007 12:49 pm
-
- Ebase User
- Posts: 201
- Joined: Fri Dec 20, 2013 1:29 pm
- Location: Dartford Borough Council
- Contact:
Finally got it working with
Hi Jon,
Finally got it working with:
jdbc:jtds:sqlserver://sql2008;instance=IDOX;DatabaseName=UniformLiveReports
Thanks for all your pointers
Neil
Finally got it working with:
jdbc:jtds:sqlserver://sql2008;instance=IDOX;DatabaseName=UniformLiveReports
Thanks for all your pointers
Neil
0 x
Who is online
Users browsing this forum: No registered users and 22 guests