March 4, 2007 at 4:08 pm
Hi,
I had a weird situation happen that I hope someone can explain for me.....I moved an SQL instance from one server to another, ie, installed SQL Server on the new server and restored all the databases, including system databases, on the new server. Everything looked ok, and I could select data from a table. When I went to create a user, I received the message "cannot resolve collation conflict". It was the end of the day, so I thought I would leave it until the next morning and fix it then, as no one would be using it. The next morning I tried to create a user and didn't get the "collation conflict" error message. The only thing I can think of is that the backups ran overnight. Could the backup have fixed this error? If only ALL my problems were this easy to solve....
thanks.
March 4, 2007 at 10:40 pm
Running backup should not resolve any of this kind issue or any other issues...
Old server and new server both has the same collations?
MohammedU
Microsoft SQL Server MVP
March 4, 2007 at 10:40 pm
Running backup should not resolve any of this kind issue or any other issues...
Old server and new server both has the same collations?
MohammedU
Microsoft SQL Server MVP
March 4, 2007 at 10:40 pm
Running backup should not resolve any of this kind issue or any other issues...
Old server and new server both has the same collations?
MohammedU
Microsoft SQL Server MVP
March 4, 2007 at 10:41 pm
Running backup should not resolve any of this kind issue or any other issues...
Old server and new server both has the same collations?
MohammedU
Microsoft SQL Server MVP
March 4, 2007 at 10:41 pm
Running backup should not resolve any of this kind issue or any other issues...
Old server and new server both has the same collations?
MohammedU
Microsoft SQL Server MVP
March 4, 2007 at 11:41 pm
I cannot check that the old server had the same collation sequence, because it has been decomissioned.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply