The other thing to know about SQL Server accounts (that often comes up along with Windows Authentication), is the ability to connect to a specific instance of MSSQL running on the same server as another (multiple or named instances).
In this case, the hostname should be specified as:
servername/instancename
Alternatively, the instance name can be specified in the url properties:
URL Property Name: instanceName
URL Property Value: <instanceName>
Most crucial in either case is to not specify a port. If a port is specified, SnapLogic will simply connect to that port without checking with the Server Browser service first.
Please note, the latest release of the jTDS driver on SourceForge was version 1.3.1, released in June 2013, supporting Microsoft SQL Server (6.5 up to 2012). The previous posts are not a recommendation or requirement to use jTDS and this post is not a recommendation against it. Whenever you consider using a third-party JDBC driver please make sure to research the documentation and open issues if public, and please reach out to SnapLogic Support if you encounter specific issues.
Hi,
for SQL Servers from 2016+, how are we supposed to user impersonate another account than the one that Snaplogic is running? As IntegratedSecurity=true, gets the server's name that snaplex runs.
