...

#Configuration created by installer
diag.dataDirectory=C:/diagserverdata/
diag.searchDirectory=C:/diagserverdata//search
diag.dbCollation=GERMAN
diag.dbDriver=com.microsoft.sqlserver.jdbc.SQLServerDriver
diag.dbUser=custodiagnostic
diag.dbPass=custodiagnostic
diag.dbUrl=jdbc:sqlserver://localhost:1433;databaseName=custodiagnostic;user=custodiagnostic;password=custodiagnostic;
diag.dbDialect=de.customed.orm.UnicodeSQLServerDialect
diag.dbShowSQL=false

Configuration - SQL Login with Integrated Security (available from custo diagnostic server version 5.8.2 on)

Before configuring the SQL authentication this way make sure that you have both the MS SQL server and the custo diagnostic server within the same Active Directory Forest or within at least a trusted domain environment. On top you will need a service account needing full rights on the custo diagnostic server and needing DB owner rights on the custo diagnostic DB on the SQL server.

...

Restart the custo diagnostic service and check the logs.

In case of problems with the SQL server certificate (you will see error messages like "javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target." in the custo diagnostic server log) and if it is acceptable for the customer's IT security (e.g. because the MS SQL server is on the same server as the custo dianostic server) you may configure as well a not encrypted DB connection: