Shulou(Shulou.com)06/01 Report--

The collation of the database is good enough to be installed by default. For example, in a simplified Chinese environment, when installing SQL Server, the default is Chinese_PRC_CI_AS, and in English, it is SQL_Latin1_General_CP1_CI_AS. In most data cases, the default option is already satisfied with our needs, but if we want to support multiple languages, we can only choose SQL_Latin1_General_CP1_CI_AS that supports unicode encoding, otherwise there will be garbled, and the application query / update data needs to be preceded by N as the symbol of the unicode character. I think many people don't pay much attention to this problem.

One example is the inconsistency between instance-level and database-level collation, which can also cause unexpected problems. For example, tempdb, which is shared by all user databases, may have problems using temporary tables or table variables if the collation of the user database is different from tempdb.

Another example is as follows (SQL Server 2008R2). The collation of the database mapped by the login name test1 is inconsistent with the collation of the instance. Open the property of the login name, the security object, and report a 468 error.

Figure-1: attribute of login name

Figure-2: 468 error reported

So it's best to use an example of database and instance collation. In database planning, it is recommended to use all SQL_Latin1_General_CP1_CI_AS, although the application needs to add N, but for future expansion, it is worth doing so.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.