I came across the following issue, when connecting to MS SQL Server databases
If there are more, than one database engines running, one can specify which one to connect to in the "Additional JDBC Parameters" of tMSsqlRow with "instance=<database instance name", e.g. "instance=SQLEXPRESS" for the default instance of MS SQL Express.
See screenshot below.
This works fine, if there are more than one database engine instances running on SQL server. However surprisingly this does not work any more, if there is only one instance running. In that case one has to specific "" in "Additional JDBC Parameters" to succeed connecting to the database. This is a little bit awkward, because my job should connect to different database servers, with each of them having one or more than one instances running. My current workaround is to selectively fill "Additional JDBC Parameters" correctly using a context variable, with a context choosen depending on the target database. However this is quite a source of errors.
Did anyone come across this problem? Is there a better way to connect to the right SQL server enging, or is this maybe a bug, that needs fixing?
Many thanks in advance!
* The exactly same job works fine,
- if there is more than one database instance - which actually demonstrates to me, that the job should be ok
- or I enter "" in the "Additional JDBC parameter"
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema