![]() ![]() It assumes that the Collation will be changing across all levels (Instance, Database, and column) since one of the two methods for changing the Instance-level Collation will change all levels. The following should be a mostly-complete list of affected areas. But first, before seeing how to change an Instance’s Collation, it is important to understand exactly what the total impact of that change could be. There are two ways to accomplish this: one “official” and the other “unofficial”. People sometimes try to “fix” this problem by adding the COLLATE DATABASE_DEFAULT to string columns of temporary tables, and/or COLLATE keyword is inadequate or undesirable, there is the option of changing the Instance-level Collation. This can often lead to unexpected errors and/or sorting and comparison behavior. For various reasons, people sometimes find themselves in the unfortunate (and unenviable) situation of having a SQL Server Instance and/or Database configured with the wrong Collation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |