Comments on: SQL Server and Collation settings http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/ Thoughts. Comment. Opinion. Wed, 07 Jan 2009 03:33:38 +0000 http://wordpress.org/?v=2.6.2 By: Grant S http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/#comment-21717 Grant S Thu, 29 Nov 2007 21:03:10 +0000 http://www.leyton.org/diary/2004/08/12/sql-server-and-collation-settings/#comment-21717 <p>Another approach in SQL Server 2005 is to simply assign the desired collation to whichever column(s) in the temporary tables require it. You can use the COLLATE keyword with "database_default" to explicitly assign the current database's collation setting to a column in a temporary table. Ex:</p> <p>create table #MyTemp ( ListItem varchar (200) COLLATE database_default ) </p> <p>This solves the "Cannot resolve collation conflict for equal to operation." error.</p> Another approach in SQL Server 2005 is to simply assign the desired collation to whichever column(s) in the temporary tables require it. You can use the COLLATE keyword with “database_default” to explicitly assign the current database’s collation setting to a column in a temporary table. Ex:

create table #MyTemp
(
ListItem varchar (200) COLLATE database_default
)

This solves the “Cannot resolve collation conflict for equal to operation.” error.

]]> By: info http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/#comment-21392 info Sun, 11 Nov 2007 15:41:49 +0000 http://www.leyton.org/diary/2004/08/12/sql-server-and-collation-settings/#comment-21392 <p>How to get rid of this message when using application thru SQL ODBC DNS-connection using English and Arabic with SQL 2005 server..</p> <p>[Microsft] ODBC SQL Server Deriver Cannot resolve the collation conflict between "Arabic<em>BIN" and "SQL</em>Latin1<em>General</em>CP1256<em>CS</em>AS" in the equal to operation. ODBC SQL Server Driver cannot resolve the collation conflict</p> <p>any suggestion thanks in advance</p> How to get rid of this message when using application thru SQL ODBC DNS-connection using English and Arabic with SQL 2005 server..

[Microsft] ODBC SQL Server Deriver Cannot resolve the collation conflict between “ArabicBIN” and “SQLLatin1GeneralCP1256CSAS” in the equal to operation. ODBC SQL Server Driver cannot resolve the collation conflict

any suggestion
thanks in advance

]]> By: Seb http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/#comment-21087 Seb Sun, 07 Oct 2007 04:52:26 +0000 http://www.leyton.org/diary/2004/08/12/sql-server-and-collation-settings/#comment-21087 <p>Yeah, I agreed with Patrice with selecting "1252 Character Set" instead of installing MS SQL Server 2005 Developer Edition with "default General Latin...".. helps me.</p> <p>In short, I now understands that the default "General Latin..." in my Notebook will install my server collation as "Latin1<em>General</em>CP1<em>CI</em>AS" not what I needed (preferred "SQL<em>Latin1</em>General<em>CP1</em>CI_AS:")</p> <p>Just to ellaborate a bit... Using MS SQL Server 2005 Developer Edition installation CD, What I tried installing with the default "General Latin.." and I ended up with the server collation as Latin1<em>General</em>CP1<em>CI</em>AS.. With this collation it caused all of my ASP.Net projects to have "Collation conflicts" problems whenever I exec the Stored Procedures... </p> <p>This really fixed it.. Thanks Patrice !</p> Yeah, I agreed with Patrice with selecting “1252 Character Set” instead of installing MS SQL Server 2005 Developer Edition with “default General Latin…”.. helps me.

In short, I now understands that the default “General Latin…” in my Notebook will install my server collation as “Latin1GeneralCP1CIAS” not what I needed (preferred “SQLLatin1GeneralCP1CI_AS:”)

Just to ellaborate a bit… Using MS SQL Server 2005 Developer Edition installation CD, What I tried installing with the default “General Latin..” and I ended up with the server collation as Latin1GeneralCP1CIAS.. With this collation it caused all of my ASP.Net projects to have “Collation conflicts” problems whenever I exec the Stored Procedures…

This really fixed it.. Thanks Patrice !

]]> By: Patrice http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/#comment-19667 Patrice Mon, 16 Apr 2007 16:37:16 +0000 http://www.leyton.org/diary/2004/08/12/sql-server-and-collation-settings/#comment-19667 <p>Hi,</p> <p>I add to choose the "1252 Character Set" for me to get the SQL<em>Latin1</em>General<em>CP1</em>CI_AS collation.</p> <p>Apart of this, your information did work great for me.</p> <p>Best regards,</p> Hi,

I add to choose the “1252 Character Set” for me to get the SQLLatin1GeneralCP1CI_AS collation.

Apart of this, your information did work great for me.

Best regards,

]]> By: Craig LB http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/#comment-19587 Craig LB Wed, 11 Apr 2007 16:34:27 +0000 http://www.leyton.org/diary/2004/08/12/sql-server-and-collation-settings/#comment-19587 <p>Hi Rose,</p> <p>I've used this before to accomplish that :-</p> <p>ALTER DATABASE MyDatabase COLLATE </p> <p>Hope it helps</p> <p>Regards</p> Hi Rose,

I’ve used this before to accomplish that :-

ALTER DATABASE MyDatabase COLLATE

Hope it helps

Regards

]]> By: Rose http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/#comment-19322 Rose Mon, 26 Feb 2007 16:37:38 +0000 http://www.leyton.org/diary/2004/08/12/sql-server-and-collation-settings/#comment-19322 <p>OK .. that is when the SQL installation was wrong ... I have things reversed. My new SQL environment is SQL_Latin1 ... but I have an older database that is Latin1-general ... how do I change just one db?</p> OK .. that is when the SQL installation was wrong … I have things reversed. My new SQL environment is SQL_Latin1 … but I have an older database that is Latin1-general … how do I change just one db?

]]> By: Asghar http://www.leyton.org/2004/08/12/sql-server-and-collation-settings/#comment-19321 Asghar Tue, 07 Nov 2006 14:45:58 +0000 http://www.leyton.org/diary/2004/08/12/sql-server-and-collation-settings/#comment-19321 <p>I am replicating three databases between two sql 2005 servers two of them are replication fine even though they are different collations but one db is giving me this error so I believe I would be reinstalling sql again :(.</p> I am replicating three databases between two sql 2005 servers two of them are replication fine even though they are different collations but one db is giving me this error so I believe I would be reinstalling sql again :(.

]]>