SA0161 : Current database uses old SQL Server collation. To take full advantage of SQL Server features, for new development change the default installation settings to use Windows collations
The topic describes the SA0161 analysis rule.
Current database uses old SQL Server collation. To take full advantage of SQL Server features, for new development change the default installation settings to use Windows collations
The rule checks context database and reports when SQL Server collation is used by the database.
While the SQL Server Collations have not been officially deprecated, they mainly exist for backwards compatibility and it is highly recommended that newer Windows Collations should be used unless there’s a pressing need to use a SQL Server Collation.
During SQL Server setup, the default installation collation setting is determined by the operating system (OS) locale. You can change the server-level collation either during setup or by changing the OS locale before installation. For backward compatibility reasons, the default collation is set to the oldest available version that’s associated with each specific locale. Unfortunately, the default Collation for new installations is a SQL Server Collation — SQL_Latin1_General_CP1_CI_AS and it isn’t always the recommended collation. This default Collation is likely the root cause for the common performance problems due to mismatching data types causing “implicit conversions”.
Take in consideration the possible problems that using old SQL Server collation instead of Windows Collations can produce. When planning a new work and new server installation, it is recommended to use Windows Collations if possible.
The rule has a ContextOnly scope and is applied only on current server and database schema.
Rule has no parameters.
The rule requires Analysis Context. If context is missing, the rule will be skipped during analysis.
Design Rules, Deprecated Features, Bugs