April 3, 2006 at 12:58 pm
We have an oddball case-sensitive Server Collation due to the original application (Application 'A') installed years ago. It's the only DB that uses that collation, and it's a pain because any new databases need to have the collation changed when they are created, and code for Application 'B' or 'C' developed on a non-case sensitive server sometimes needs to be fixed to work on the production server.
We're going to be replacing that server soon, so I figured this would be a good time to change the default collation. All our user databases are on a SAN, but Master, MSDB & Model and the logs are local on the server. We'll install SQL on the new box, and point it to the SAN, but what about the system databases, and changing the default collation ? What "gotchas" should we look out for ?
April 5, 2006 at 11:27 am
I don't know about 'gotchas' but we have the same issue. So I am building another instance on the non-production server for testing. It seems to be just as easy !
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
April 5, 2006 at 11:43 am
What are you doing with the system databases ? Just save & restore ?
April 5, 2006 at 12:51 pm
New instance implies new system databases and all the associated maintenace, plans, etc. that would be needed just as if one had built a new server. Not a terribly large amount of work when you really think about it since the physical server, network connections, SAN conenctions and backup infrastructure have already built, configured and functioning. I've allocated about 2 hours for the whole process and will be undertaking it on Friday this week.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply