![]() The method I speak of is running sqlservr.exe with the -q switch. Also, there are two areas that are currently not updated by this approach, though I have requested that they be added, so please vote for this suggestion: Update Collation of Partition Functions and User-Defined Table Types via SQLSERVR -Q. However, this is a non-issue if the code page isn't changing. The major issue is that by changing the collation_id, any existing VARCHAR characters in the range of 128 - 255 might be misinterpreted in the new collation. Plus it changes the system DBs and the instance-level collation. ![]() And it bypasses all of the restrictions that prevent updating a databases collation (in many, but not all, cases). The only real time spent is in the rebuilding of all affected indexes. It merely updates the internal collation_id of each string column in the metadata (for system tables that should be updated and all user tables). In fact, this undocumented approach is incredibly fast because it does not move any data at all. either not changing code pages or changing code pages but no characters being used are different between the code pages and this only pertains VARCHAR data), then there is an undocumented option that might be much quicker, both in terms of time spent working out the solution, and time spent moving data. ![]() ![]() If no code page conversions are necessary (i.e. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |