November 12, 2009 at 4:45 am
Hello,
While creating the new user from Enterprize Manager I get an error
"Error 446:Cannot resolve collation conflict for equal to operation".
But the user gets created using sp_adduser.
What should be the problem and how to resolve it?
Thank you.
Regards,
Rohit
November 12, 2009 at 4:55 am
your database is not created with the same collation as your sqlserver instance itself.
How to resolve it ?
This issue goes further that just with sp_adduser.
It basically means your db has other language settings than your system databases. As long as you don't use multidatabase queries, you should be fine.
However, if you do need multi database queries, you need to resolve this collation conflict every time you are comparing (var)char columns.
If this is the only database on your instance having this collation conflict, you could investigate your applications to see if they really need the set collation. If not, you can "migrate" the data to a database of the correct collation and perform the collation conversion only during this migration.
edited:
SQL2000 allows multiple collations per instance, but I prefer only having a single one on my instances.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 12, 2009 at 5:13 am
I checked the collation of the instance (right click SQL Server registration->properties->General->Server Collation.
It is SQL_1xCompat_CP850_CI_AS which is same as database collation
November 12, 2009 at 5:21 am
it is possible your default collation of the userdb has been altered.
Script the dbo.sysusers table of the userdb including collation information.
You may find a different collation,..
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 12, 2009 at 9:15 pm
I did not change any collation related setting. Default collation is same as the current one.I suspect one thing that might have caused the problem.We were trying to migrate the system to SQL 2k8.We had installed SQL 2k8 on this server.But due to time constraint we decided not to go with SQL 2K8 but to continue with SQL Server 2000.Then SQL 2K8 was un-installed and SQL 2000 was installed. It is after this reinstallation that we are facing the problem.
I will uninstall SS2K again.
Uninstall anything related to SQL Server.
Manually delete any folder related to SS.
Install SS2K and it's latest service packs and hot fix.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply