.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_

Posted By:      Posted Date: May 22, 2011    Points: 0   Category :

Error:Msg 468, Level 16, State 9, Procedure CreditRecal1_Update, Line 50
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AI" in the equal to operation.

 Update m Set m.CreditLeft = t.CreditLeft
 From mMemberProfile m Inner Join #Temp t On t.UserId = m.UserId
 Inner Join mMemberTree mt On mt.UserId = t.UserId
 Where mt.[Role] = 'MEM'

Why is it so?

View Complete Post

More Related Resource Links

collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS"


Hello Everyone,


I am getting the following issue when u am running my query. Can anyone please tell me what i need to do on this to resolve.


Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation



Anil Kumar

Server Collation SQL_Latin1_General_CP1_CI_AS versus Latin1_General_CI_AS

Hi,Why does SQL Server 2005 sometimes install with a server collation of :Server Collation SQL_Latin1_General_CP1_CI_AS and other times a server collation of :Latin1_General_CI_ASWhat causes this ???What is the difference between the two ?Are there any problems restoring databases from one to the other ? Do the two different collations cause problems with applications ?

Collation SQL 2005 sql_latin1_general_cp1_ci_as

Hi, Our application uses SQL 2005 database with Latin1_General_CI_AS as collation. There are nearly a million records in this database. I need to move my data to another SQL 2005 server which has 'SQL_Latin1_General_CP1_CI_AS ' as collation. I know there would be lots of issues. Do you know what are the likely issues that we would face. Since there are lots of modules dependent on this database, it would be difficult to test each and every component if all works ok or not. Is this advisable to move to another database with this non standard SQL_Latin1_General_CP1_CI_AS  collation?   thanks sANDY  

collation conflict error in BCP Query out


I am using BCP out command to export data to text file from SQL Server database using code below 

select @sql = 'bcp <tableName> out C:\bcp\image.txt -c -t$$ -b 10000 -UDBA -Pxxxx -S'+@@servername

Exec master..xp_cmdshell @sql, no_output 

I am getting the following error sporadically 

SQLState = 37000,

On SQL_Latin1_General_CP1_CI_AS SQL Server 2008 Default Collation


Collation is one of the most confusing features of SQL Server. BOL 2008 states that backward compatibility is the only reason to go with SQL collation. I thought previously it is just smart to stay with the default Microsoft offers unless there is a real good reason to choose a different collation.

So is the default SQL_Latin1_General_CP1_CI_AS  (Case Insensitive, Accent Sensitive) a good choice? (Assume the installation is brand new SQL Server 2008)

Related links:

SQL Server offers the SQL_Latin1_General_CP1_CI_AS collation as the default collation for server installations.

For backward compatibility, the default English-language (US) collation is SQL_Latin1_General*.

Kalman Toth, SQL Server & Business Intelligence Training; SQL 2008 GRAND SLAM

how to resolve conflict when using sql service broker to do bidirectional replication?


greetings ,,

after spending days in search about the best practice to make bi-directional replication between 2 databases on 2 distributed sql server instances ,,i have found that sql server service broker is the most suitbale with my business req to use as i have a problem with the updatable subscrption replication due to leased line between networks in 1 MEGA and it will be large amount data that will be replicated and that will not work as the latency will increase ,,but i need some help to know how can i resolve these conflicts when i am using sql server broker service:

1-If you insert a record that has a key into a table on one of the servers and another record that has the same key already exists on the other servers that participate in the replication, the replication does not propagate the changes to the other servers.

2-When you update a column in a record that is updated at the same time on another server, the data may be different on the two servers.

3-When you update different columns in a record, simultaneous updates of different columns of a record may sometimes lead to conflicts.

4-When you delete a row that is being deleted at the same time on another server that is participating in the replication, the replication fails because the DELETE statement does not affect any rows on some of the subscribers.


The XML Files: XSLT Keys, Select vs. Match, Conflict Resolution, and More


This month Aaron Skonnard covers how keys work in XSLT, XSLT match and select attributes, SelectNodes order, finding