Changing Server Collation on SQL Server 2008

Question

Post reply

Changing Server Collation on SQL Server 2008

Viewing 7 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic. Login to reply

blessonblessons SSC Eights! Points: 959 More actions · Answer 1

The log file will be placed in the folder:-

C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log

philip.kraft Old Hand Points: 327 More actions · Answer 2

Thank you again John for all the help! Do you perhaps have an email address I can forward the logs to?

blessonblessons SSC Eights! Points: 959 More actions · Answer 3

No worries Phil,my email address is blessonblessons@yahoo.com.

afterx SSC Enthusiast Points: 161 More actions · Answer 4

philip.kraft you can run this on sql 2005, 2008, and 2008 R2. You just have to make sure the server collation is different from the one you want to go to. More information can be found Here[/url]

-JM

wjewell Valued Member Points: 55 More actions · Answer 5

sqlservr -m -T4022 -T3659 -q"SQL_Latin1_General_CP1_CI_AS" -sSQLEXPRESS

Thanks for the command. I used it on my sqlexpress 2012 version. Just had to stop the instance, ran the script and then started my instance again.

Thanks Agian

Solomon Rutzky SSCoach Points: 16430 More actions · Answer 6

Hi there. Regarding item # 12 in the article:

12) All the databases that had user defined assemblies should have 'trustworthy' set to true.

Please do not enable TRUSTWORTHY on databases, especially in Production. It is neither desirable nor necessary, at least not on a permanent basis (please see the following post of mine which describes the various issues related to TRUSTWORTHY: PLEASE, Please, please Stop Using Impersonation, TRUSTWORTHY, and Cross-DB Ownership Chaining ). However, it is sometimes required to enable temporarily in order to implement proper security (and those instances would be greatly reduced if Microsoft would implement the following suggestion, so please vote for it: Allow Asymmetric Key to be created from binary hex bytes string just like CREATE CERTIFICATE ).

What it comes down to is this: assemblies should be signed. And if assemblies are already loaded and cannot be signed prior to loading into SQL Server, you can still sign them within SQL Server (i.e. without exporting / re-importing). Please see the following post of mine that describes this and provides a working example: SQLCLR vs. SQL Server 2017, Part 4: “Trusted Assemblies” – The Disappointment (Msg 10314).

Finally, for a thorough description of what the "sqlservr.exe -q" option does and does not do, please see my post:

Changing the Collation of the SQL Server Instance, the Databases, and All Columns in All User Databases: What Could Possibly Go Wrong?

Take care,

Solomon..

SQL# — https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
Sql Quantum Lift — https://SqlQuantumLift.com/ ( company )
Sql Quantum Leap — https://SqlQuantumLeap.com/ ( blog )
Info sites — Collations • Module Signing • SQLCLR

SQLRNNR SSC Guru Points: 281334 More actions · Answer 7

@solomon - Nice catch. After all these years, it is good to catch something like that. I am remiss that I missed that when I first read the article years and years ago.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events