Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Supported SQL collations

Supported SQL collations

Table of contents
Created by Su-Lyn Rosenberry, last modified by Su-Lyn Rosenberry on Feb 23, 2017

Views: 111 Votes: 1 Revisions: 6

 

Overview

SolarWinds does not support case-sensitive databases.

SolarWinds supports the following collations on the SQL Server:

  • SQL_Latin1_General_CP1_CI_AS
  • SQL_Latin1_General_CP1_CS_AS
  • German_PhoneBook_CI_AS
  • Japanese_CI_AS
  • Chinese_PRC_CI_AS

 

SolarWinds supports the following database collation:

SQL_Latin1_General_CP1_CI_AS

 

These collations are supported when the SolarWinds server locale is set to en-US and the default login language is set to us-english.  Other configurations are not supported.

Environment

Orion Platform versions running 2015.1 or later

Steps

If you do not use a supported collation, you must re-install your instance of SQL and re-install it with the correct collation.

  1. Create a backup of your data.
  2. Re-install your SQL instance with a supported collation.
  3. Re-create your tables.
  4. Import your data.


It is also possible to change SQL Server Collation manually via cmd prompt command.
Doing so would mean your DBA would need to take ownership. SolarWinds cannot take these steps as there are risks involved and DBA will need to process with care.

Process below is useful where a new SQL Instance has just been installed and no database has yet been attached or created.
 

If you need to edit the SQL Server Instance Collation without reinstalling:

1. Check Collation in SQL Management Studio:

Danish_Norwegian_CI_AS

 

2. If need to edit the SQL Instance Collation,  stop the SQL Server Instance. (You can use Services.msc, cmd or SQL Management Studio to do this)

NET STOP "MSSQLServer"

 

3. Execute the command below. The parameter -s is only necessary if more than one SQL Server instance exists on the target machine. Parameters used: 

  • [-m] single user admin mode 
  • [-T] trace flag turned on at startup 
  • [-s] sql server instance name 
  • [-q] new collation to be applied


Some SQL text will appear and at end of large amount of text will be Collation has updated successfully. From this point no user action is required, close the cmd prompt window after the execution ends.

sqlservr -m -T4022 -T3659 -s"MSSQLServer" -q"SQL_Latin1_General_CP1_CI_AI"

 

 

Last modified
19:45, 22 Feb 2017

Tags

Classifications

Public