Thursday, March 22, 2012

Collation Conflict Error 368 (I think)

We just upgraded an instance of SQL Server 2000 to SQL Server 2005. When using our application to login, we are receiving an error 368, which refers to a collation conflict. Has anyone seen this?

I'm moving your thread to the database engine forum, where it may get more attention.

Paul

|||Run the profiler to see which statement your application is issuing against the database. Are you sure you are using the same collation on the new server than on the old one ? Normally this happens if you are comparing two different collation with each other (like in joins or equal expressions).

HTH, Jens Suessmeyer.


http://www.sqlserver2005.de

|||

Unfortunately, only this message got moved for those of us using NNTP. Any chance that when you move a thread, you can mention where the thread was moved *from*, so we can see it? That will certainly increase the chance that it gets more attention after being moved. Steve Kass Drew University Paul Nicholson - MSFT@.discussions.microsoft.com wrote:
> I'm moving your thread to the database engine forum, where it may get
> more attention.
>
> Paul
>
>

No comments:

Post a Comment