Setting up SQL Server to work with HCL Discover
After installing SQL Server you need to configure it to work with HCL Discover.
Setting up SQL Server to work with HCL Discover
Use the information in Configuring SQL to work with HCL Discover - A reference table as a guideline for configuring SQL Server to work with HCL Discover. Consult SQL Server documentation for specific instructions with regard to configuring SQL server.
Things to do | Notes |
---|---|
Check the amount of RAM allocated to the SQL Server. |
For a single-server topology, no more than 2 GB of the system RAM should be allocated to Microsoft SQL. |
Connect to the Server |
Login to SQL is managed via the Microsoft SQL Server Management Studio. A login screen is displayed that allows you so specify the HCL Discover Server name and click Connect. Note: If
the Database Administrator completed a non standard configuration,
you will need details from the administrator. If after clicking Connect you are not connected to the database, contact the database administrator. The database administrator can provide you with the information needed to authenticate with the database. |
Configure SQL Server Consumption |
Set and confirm that your instance of SQL Server is configured to consume no more than 50% of the server's RAM. |
Configure SQL Server for Mixed Authentication Mode | The following instructions are a guideline. Consult your Microsoft SQL Server documentation or articles from the MSDN for specific instructions.
|
Configuring Custom Password for DCADMIN/DCUSER in SQL Server | To set up a custom password for the DCADMIN/DCUSER
users in SQL Server, complete the following steps:
|
Configure SQL Server for TCP/IP Protocol Support | The following instructions are a guideline. Consult your Microsoft SQL Server documentation or articles from the MSDN for specific instructions.
|
Configuring SQL Server for DATABASE Port 1433 | Ensure that the TCP DYNAMIC PORTS is not enabled. If the database has been configured using dynamic ports contact will again be needed with the local database administrator to have them disabled. |