Configuring Microsoft SQL Server
Database setup is done on the Microsoft SQL server.
Be certain to read the pre-installation notes for SQL Server provided in this documentation.
The SQL Server installation has to be an AccentSensitive, CaseInsensitive, Unicode-ready installation.
- If you are doing a fresh SQL Server installation make sure that in the Database engine Collation settings, Accent-sensitive is selected and Case-sensitive is not selected.
The typical Content Manager collation is SQL_Latin1_General_CP1_CI_AS (not the often mistaken collation Latin1_General_CI_AS). Depending on the SQL Server version, the collation SQL_Latin1_General_CP1_CI_AS is also displayed as Dictionary order, caseinsensitive, for use with 1252 Character Set.
- You can check the collation name by issuing a query in SQL Server Management Studio connected to your server.
- Click New Query then enter:
select ServerProperty('Collation'). - Click Execute.
- Verify that the result shows an Accent-sensitive (AS), Case-insensitive (CI) collation name.
For more information refer to Collations in the SQL Server help files.
- Click New Query then enter:
Authentication based on named SQL Server login ID and on Windows accounts is recommended.
- Check or modify this in SQL Server Management Studio, right-click ServerName, then click Properties and select Security on the left pane.
- In the Server authentication pane on the right, select SQL Server and Windows Authentication Mode.
SQL Server Agent is part of the SQL Server software.
- Check that this Windows Service is set to automatically start upon server reboot.
Windows 2012: In the Control Panel click Administrative Tools then double-click on Services.
- Verify that SQL Server Agent start up type is Automatic.
To execute database transactions, the Microsoft Distributed Transaction Coordinator (MSDTC) settings of the database server have to match the ones on the application server. All servers require a reboot before these settings become active.