January 29, 2012 at 6:48 pm
OK. Here's a question. I have a client that is running Documentum on a SQL 2005 server. The server is set up case-insensitive (SQL_Latin1_General_CP1_CI_AS) but now the client says this is wrong, and the server needs to be case-SENSITIVE (SQL_Latin1_General_CP1_CS_AS, presumably).
Here's the MS documentation on changing case sensitivity at the SQL Server level: http://msdn.microsoft.com/en-us/library/ms179254.aspx. UGH! It says I have to script out and rebuild all SQL objects with scripts afterward and then BCP in all the data, for each database. Pain in the butt.
I note that all the actual Documentum databases ON the server already ARE set to be case-insensitive (SQL_Latin1_General_CP1_CS_AS) -- they were that way, I imagine, when the were restored form the previous, older, server.
So here's my question: If I do have to rebuild the master database (or SQL Server, whichever), since the databases are ALREADY SQL_Latin1_General_CP1_CS_AS, can I first just detach them and beforehand and reattach them after and be done with it? Or maybe not even that, just leave them in place and recreate the master database?
Any feedback on this is greatly appreciated.
Thanks.
G. Milner
January 29, 2012 at 8:17 pm
If the user databases are/always were CASE SENSITIVE, you won't need to re-create them. Just detach and re-attach
January 29, 2012 at 8:21 pm
Good to know. Thanks!
G. Milner
January 30, 2012 at 2:16 am
Here's an alternative way to change the server collation. http://spaghettidba.com/2011/05/26/changing-server-collation/
Read the "An undocumented method" paragraph.
-- Gianluca Sartori
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply