Collation Conflict

[barbola]

Ugh we moved Great Plains to a new server, and thought we had the correct sort order. BUT as it turns out, this is what we have:

"servername" Latin1_General_CI_AS
DYNAMICS SQL_Latin1_General_CP1_CI_AS
"company" SQL_Latin1_General_CP1_CI_AS
master Latin1_General_CI_AS

Can I do this:

ALTER DATABASE master COLLATE SQL_Latin1_General_CP1_CI_AS

and if so, how do I get "servername" collation to change? We are DOWN until I get this resolved and our vendor is oh so helpful as always.



Thanks!
Barb E.

 

[stef315]

I would reinstall SQL with the correct (SQL_Latin1_General_CP1_CI_AS) sort order then restore the databases.

 

[barbola]

Do I need to recreate the databases first? This took me ten hours on Saturday.

We thought we DID select the correct sort order. How do we get the SQL_ in front of it as well as the CP1?

Can I use Rebuildm.exe?

Thanks!
Barb E.

 

[barbola]

After I use rebuildm.exe will this make my company databases disappear, and then can i use this:

EXEC sp_attach_db @dbname = N'test_database', @filename1 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\test_database.mdf', @filename2 = N'c:\Program Files\Microsoft SQL Server\MSSQL\Data\test_database.ldf'

Thanks!
Barb E.

 

[barbola]

After talking to our vendor, we decided to use Rebuildm.exe to rebuild the master. I was getting a sharing violation.

Then it ran and I got "failed with error -1". I had moved the db's to the proper directory, and tried again but get sharing violation.

In rebuild, it asks to enter the path to the data but below that it shows a path that is different, and we can't change that one? Help?

For now we reverted to the old server, and will be back at square 1 with new backups and restoring to the new server tonight.


Thanks!
Barb E.