For MS SQL you have
to add the following additional parameter in the Connection object:
I have a MS-SQL
Server (a named instance) and connect with my SQLDBSERVICE Agent (which is
started with my Windows Login) successfully with the following settings in the
Login Data: <Windows
| Connection Properties:
IntegratedSecurity | Value: true
I've done this with the jdbc connection used by the JWP and JCP, but on one system the ;integratedSecurity=true was not added to the connection string (ucsvr.ini) and on the other it was needed. (also the sqljdbc_auth.dll was placed on the AutomationEngin\bin).
I would say that one of the system is a test, where the security is not so high and the other is Prod, so there are maybe so additional policies.
Hi,maybe a bit late but maybe this is helpful for some users.SQL Agents are Java-based Agents. JDBC is used for connectivity to any database type.Windows authentication for SQL Server (AD domain user) requires either Kerberos or NTLM authentication.The SQL Agent (v 12.2) only supports this when the agent itself is started as the connection user (Service Manager Dialog > Run As setting). Also in the agents ini-file the windows authentication must be 1 (default is 0).An undocumented workaround is to add the following advanced properties in the connection object (on the right for connection properties extensions):authenticationScheme = NTLMdomain = <your_ad_domain>userName = <username_without_domain>integratedSecurity = trueThe password is taken from the login object assigned to the job.Also the newest microsoft jdbc driver version is necessary.Another workaround is to utilize the Generic JDBC datatype:Connection String = jdbc:sqlserver://<db-name:port>;databasename=<db_name>;integratedSecurity=true;authenticationScheme=JavaKerberos;userName=<user@domain>;password=<password>The agent needs to run as any authentication domain user for that.Alternatively the authenticationScheme=NTLM should also work here (not tested.)Hope this helps someone.BRMarcel