SQL: Collation and Compatibility

Compatibility Mode 90

SQL must be in Compatibility Mode 90 (SQL 2005) or greater to support .NET Assemblies.

• sp_dbcmptlevel 'ksubscribers'  - Running this stored procedure displays the compatibility level.
• sp_dbcmptlevel 'ksubscribers', 90 - Running this stored procedure sets the compatibility level to SQL 2005. If you are using SQL Server 2008, do not run this stored procedure.

Collation

• Collation Matching - The Kaseya Server requires the collation selected for each of the following match each other.
  • The SQL Server master database.
  • The SQL Server dbtemp database.
  • The Kaseya ksubscribers database.
• Case Insensitivity - The Kaseya Server also requires the selected collation be case insensitive.
• Collation Selection
  • The default collation setting selected by SQL installer is determined by the Windows default system language (System locale setting).
  • Kaseya strongly recommends the language of your Windows operating system match the primary language you intend on using in the VSA.
  • During the installation of SQL Server, ensure the collation selected for your SQL Server installation corresponds to the primary language you intend on using in the VSA.
    • For all single-byte language installations, including English, set the collation to: SQL_Latin1_General_CP1_CI_AS
    • For Korean installations, set the collation to: Korean_Wansung_CI_AS
    • For Chinese installations, set the collation to: Simplified Chinese - Chinese_PRC_CI_AS, Traditional Chinese can be either: Chinese_Taiwan_Stroke_CI_AS (more common) or Chinese_Hong_Kong_Stroke_90_CI_AS
    • For Japanese installations collation, set the collation to: Japanese_CI_AS

    Note: Changing the collation for SQL Server after it is installed requires expertise. If the collation for the SQL Server must be changed after SQL Server is installed, Kaseya recommends uninstalling SQL Server entirely, then reinstalling SQL Server and selecting the correct language to make the change.

    Note: If changing the collation of the ksubscribers database is required, reinstall SQL Server and select the correct collation of the ksubscribers.