Master Database Collation issue
From: kalamos (kmcclare_at_hotmail.com)
Date: 10/28/04
- Next message: Tony Rogerson: "Re: Delete without log ??"
- Previous message: GYK: "Re: Delete without log ??"
- Next in thread: Tibor Karaszi: "Re: Master Database Collation issue"
- Reply: Tibor Karaszi: "Re: Master Database Collation issue"
- Reply: Sasan Saidi: "RE: Master Database Collation issue"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 28 Oct 2004 15:15:36 -0400
Let me start from the beginning.
SqlServer was installed with default settings which meant:
SQL_Latin1_General_CP1_CI_AS
Later a third part application was added that created a database with this
collation: Latin1_General_CI_AS
According to the vendor SqlServer should have been installed with the
Latin1_General_CI_AS collation settings.
The question is how do I change master, tempdb, model etc from their
existing SQL_Latin1_General_CP1_CI_AS to Latin1_General_CI_AS ?
One solution was to install another instance of sqlserver with the proper
collation and just copy these databases over the ones that are in error.
Bring up the server and "Business as Usual".
Will this work? It seems to. What failures can we expect?
tks
ken.mcclaren@charter.net
- Next message: Tony Rogerson: "Re: Delete without log ??"
- Previous message: GYK: "Re: Delete without log ??"
- Next in thread: Tibor Karaszi: "Re: Master Database Collation issue"
- Reply: Tibor Karaszi: "Re: Master Database Collation issue"
- Reply: Sasan Saidi: "RE: Master Database Collation issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|