|
Hi We made mistake when we installed SQL Server 2008 with wrong collation. I know it's n't recommended to change the Collation on server level,But What is the opinion of the experts on this site it's recommended to change the collation on the server level ? and what is the best way to do that?
(comments are locked)
|
|
As recommend by Microsoft, http://msdn.microsoft.com/en-us/library/ms179254(v=sql.105).aspx, I think that I would either a) Reinstall with the correct Collation or b) Change the collation of the new databases. Given that option 'B' I think would get confusing and most likely a database would be missed and cause havoc later in life, I would most likely opt for a complete reinstall. Do you already have user databases on the server and is it in production? Just my opinion though. Yes this is the problem we have already users db and the server in production .
Dec 10 '12 at 03:32 AM
Troy_2012
How many databases are we talking about?
Dec 10 '12 at 03:38 AM
JohnM
just one database and it's mirror
Dec 10 '12 at 04:51 PM
Troy_2012
In that case, I'd opt to scripting out the mirroring configuration , schedule an outage, backup the database, and nuke & pave the instance. Once the instance has been reinstalled & reconfigured, you can restore the database and re-configure mirroring via the script. Just a thought.
Dec 10 '12 at 05:00 PM
JohnM
(comments are locked)
|
|
Seriously, go for the re-install option. Collation issues are a major ball-ache for an incoming DBA, so much so that I contributed a test in @Brent Ozar's sp_Blitz - http://www.brentozar.com/blitz/ - http://www.brentozar.com/blitz/database-server-collation-mismatch/
(comments are locked)
|
|
Reinstalling with correct collation is the only solution check the below link http://sqlbuzz.wordpress.com/2011/08/20/how-to-rebuild-master-database-aka-rebuilding-sql-server-2008r2/
(comments are locked)
|
