Description

The Microsoft SQL Server is a very powerful Database System. The Microsoft SQL is used in small and large Environments. Its very easy to install and to manage. custo diagnostic 5.x Setup does not deliver the Installation Source for Microsoft SQL. The Microsoft SQL has to installed by manual, or by customers IT Administration.

Usage

The Microsoft SQL Database in custo diagnostic can be used for every custo diagnostic Environment. Its suitable for:

• Satellite Workstations
• Small network based Installations
• Middle network based Installations
• Big network based Installations
• Cross-site Installations
• Unlimited concurrent Users
• Unlimited Number of concurrent Workstations

Restrictions

The Express Edition of Microsoft SQL Server hat the 10 GB Database Size Restriction (from Microsoft SQL 2008 Express). So if you want to use custo diagnostic with a larger Database, you have to use the Microsoft SQL Server instead the Express Edition.

Connecting to MS SQL server

There are 2 ways to connect to the MS SQL server:

a) With a SQL service account

b) With a MS Windows Active Directory service account via the integrated security.

Connection via SQL service account

Make sure that the MS SQL accepts the SQL server local account authentication, create a DB (e.g. custodiagnostic) and a local SQL service account which should have owner rights for the DB. Then enter the information about the DB in either the setup dialog of the custo diagnostic server or modify the diag.properties file while the custo diagnostic service is stopped. It should look then like this:

#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.

With those prerequisites fulfilled stop the custo diagnostic service and change the service to run with the service account. Afterwards restart it and verify that it runs properly. If so stop the custo diagnostic service again.

Adapt the diag.properties file this way:

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: