Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
24 views1 page

SQL Database Collation Guide

The document discusses running scripts to re-collate databases and tables after changing the default collation at the database level. It provides the T-SQL used to generate re-collation scripts for specific databases, notes that the index rebuilds took a long time, and recommends running the scripts twice to ensure everything is recollated properly. It also describes how text columns require being dropped and recreated manually.

Uploaded by

hanuman sqlboy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
24 views1 page

SQL Database Collation Guide

The document discusses running scripts to re-collate databases and tables after changing the default collation at the database level. It provides the T-SQL used to generate re-collation scripts for specific databases, notes that the index rebuilds took a long time, and recommends running the scripts twice to ensure everything is recollated properly. It also describes how text columns require being dropped and recreated manually.

Uploaded by

hanuman sqlboy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

Not sure what happended here or how you did the recollation.

Did you run an


existing script, or did you generate a new one? There were some in PGAS and a lot
in QFCPGAS that carried the wrong collation. You cannot just change the default
collation at the database level.

I ran the following in the PGAS and QFCPGAS databases to generate re-collation
scripts, then (carefully) ran the results. The index rebuilds in PGAS took a long
time to complete.

Use <dbname>

Go

Exec sp_recollate_database @collation = ‘Latin1_General_BIN’

Go

Also, whenever I do this, I always run it again after it completes. If the proc
doesn’t come back and say something like “No objects require recollation”, it may
need to be run again. Also, just be aware, after dropping all the Fkeys, indexes,
Pkeys, etc., the guts of the generated script is to do an ALTER TABLE ALTER COLUMN
on every single char/varchar column to change the collation. Columns using the text
datatype (there are a few) cannot be altered. For these, that table needs to be
dropped/re-created manually. For these, I use EXEC sp_tus <tablename>. You can just
run its output.

Glen
N:\Database_Admin\Knowledge_Base_for_DBA_Info\SQL Server\Database Collation Change

You might also like