Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
homebrew
Posting Yak Master
114 Posts |
 Posted - 2006-04-03 : 16:17:08
|
| 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 ? |
|
|
bakerjon
Posting Yak Master
145 Posts |
Posted - 2006-04-06 : 10:43:05
|
| Have you tried creating a separate instance for the oddball collation instance? You could have all normal collation DBs running on one instance while the oddball runs on the other one. Just a thought. The only gotcha I can think of is TEMPDB. I've had problems with it's collation being different than other databases on the server. If you are asking how to change collation on the existing system databases, I'm thinking that's dicey. I'd probably opt for scripting out users and jobs and moving them to a fresh install. That's my $0.02.JonHolding it down on the engineering tip, y'all!http://www.sqljunkies.com/weblog/outerjoin |
 |
|
|
|
|
|
SQL box replacement & collation