Define the connection to the control database using either an ODBC data source (DSN) or a connection string (recommended).
The database should be created in advance; SQDR Configuration can only create control tables, not the database itself.
For an IBM Db2 LUW database, you can use either StarSQL (recommended) or the IBM DB2 ODBC driver.
For a Microsoft SQL Server control database, you can use the Microsoft ODBC Driver 17 or 18 for SQL Server.
Use Windows integrated security is supported only for a SQL Server database; note that SQDR Configuration will be run using the userID of the user running the application, but the SQDR service will be using the userID that is running the service, so make sure that both users have appropriate authorities in the database.
Here are some sample connection strings:
StarSQL
Local database:
Server=SQDRC;hostname=localhost;port=50000;PkgColID=STARSQL
Remote database (be sure to specify the hostname or an IP address when configuring a remote service, and that that hostname resolves for the machine running the service)
Server=SQDRCXXX;hostname=mydbsys.mydomain.com;port=50000;PkgColID=STARSQL
The database (e.g. SQDRC or SQDRCXXX) must already exist.
IBM DB2 ODBC Driver
Hostname=myhostip;port=50000;Database=MYRDB;Protocol=TCPIP;Authentication=SERVER
ODBC Driver 17/18 for SQL Server
For a local default instance - any of the following:
Server=(local)
Server=.
Server=127.0.0.1
For a local named instance
Server=.\SQLEXPRESS
For a remote default instance:
Server=MYHOST
For a remote named instance
Server=MYHOST\SQLEXPRESS
For a default instance listening on a port other than 1433:
Server=MYHOST,<port>
For a named instance if SQL Browser service is not being used
Server=MYHOST,<port>\SQLEXPRESS
For an encrypted (TLS/SSL) connection:
Server=MYSERVER;Trusted_Connection=Yes;Database=MyDatabase;Encrypt=Yes;
Use Trusted_Connection=Yes to use integrated Windows security.
Use Encrypt=Yes to specify an SSL connection; use Encrypt=No or Optional to specify a non-SSL connection.
Use Encrypt=Yes;TrustServerCertificate=yes to specify an SSL connection without verifying the server certificate. This is useful if the server certificate was issued by a Certificate Authority (CA) unknown to the client machine or the connection specifies an IP address or hostname other than the Common Name defined in the certificate.