Collation conflict

Ok, Im doing a query and its all within the same database, same server etc. Looking at the database properties, the collation is set to Latin1_General_BIN, as are the individual tables. So now why would I get an error such as this?
Cannot resolve the collation conflict between "Latin1_General_BIN" and "SQL_Latin1_General_CP1_CI_AS"

Can I update the collation for a individual column?
Yes, ALTER TABLE works, but you need to drop and reapply constraints, defaults and indexes.
However, there is all reason to do it. The COLLATE clause works from a functional point of view, but for performance it can be a disaster.
Erland Sommarskog, SQL Server MVP, [email protected]

Similar Messages

Error collation conflict

I keep getting the following error with this statement
Msg 468, Level 16, State 9, Line 6
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
Statement :
SELECT Clients.biz_name,Clients.ID,Employers.Name,Employers.RefId
FROM ClientBook.dbo.Clients
JOIN za_FinCloud.dbo.Employers
ON Clients.biz_name=Employers.Name
How do I correct this ?

E.g.
SELECT Clients.biz_name ,
Clients.ID ,
Employers.Name ,
Employers.RefId
FROM ClientBook.dbo.Clients
JOIN za_FinCloud.dbo.Employers ON Clients.biz_name = Employers.Name COLLATE SQL_Latin1_General_CP1_CI_AS;
But the question is: Why do you use different collations?

Problem : Cannot resolve the collation conflict between ...

Hi
I want select a column from another database base on my current field on current database.
here is my query :
select ms.ServiceID, ms.ServiceName, ms.CoefficientFixedService,
(select Services_Name from MpAdmisson..IAServices_Table where Services_DepartmentID=24 and Services_Name=ms.ServiceName) as N'MpServiceName'
from MedicalServices ms
join MedicalCategories mc on ms.MedicalCategorizationID=mc.MedicalCategorizationID
join Zones z on mc.ZoneID=z.ZoneID
where z.ZoneID=24
but I'm facing this error :
Cannot resolve the collation conflict between "Persian_100_CI_AI" and "Arabic_CI_AS" in the equal to operation.
Also i changed collation of "MpAdmisson" db to "Persian_100_CI_AI" and even restart msSqlServer service, but i'm facing the same error!
where is my problem and how to solve it ?
thanks in advance
http://www.codeproject.com/KB/codegen/DatabaseHelper.aspx

although you changed the collation of the database it does not mean that all the objects changed their collation too automatically.
So far you are correct.
The change is only done when you change the data within the objects, thus recreating the table and moving data in / out or touching each and every value with doing something on the values themselves (the following will not work UPDATE (..) SET ServiceName
= ServiceName, the optimizer is smart enough too see that as a noop).
However, this is flat wrong. This is the story: each character column in a database has a collation tied to it. When you change the collation of a database, you change 1) the collation of the columns in the system tables. 2) The default collation. To change
the collation on the individual columns, you need to alter the column:
ALTER TABLE IAServices_Table
ALTER COLUMN Services_Name <current data type> COLLATE Persian_100_CI_AI [NOT] NULL
Unfortunately, this only works if the column is not indexed and has no constraints tied to it. Any indexes have to be dropped and recreated after the ALTER statement. If the column is a key column and there are referencing foreign keys, they also have to
be dropped and recreated. Thus, this is quite a far-reaching operation. And it may not stop there - with some amount of bad luck, constraints may fail with the new collation.
For this reason, this workaround suggested by Jens, may be your only option in the short term:
If you cannot do this currently, you can still do the following and collate on a per query basis:
select ms.ServiceID, ms.ServiceName, ms.CoefficientFixedService,
(select Services_Name from MpAdmisson..IAServices_Table where Services_DepartmentID=24 and Services_Name=ms.ServiceName COLLATE Persian_100_AS_CI) as N'MpServiceName'
from MedicalServices ms
And this part of Jens's post is correct. To note though is that use of the COLLATE clause voids any index on ServiceName. (Since this index is sorted according the rules of Arabic, and not the rules of Farsi.)
Erland Sommarskog, SQL Server MVP, [email protected]

Collation conflict error OVGT table

Hi Guys,
I get a collation conflict error as above. Server instance and company databases are now set to same collation "latin1_general_CP1_CI_AS" but still error appears.
Before that company database was on "CP850" setting.
Any ideas to resolve this?
Is there a query I can run to identify tables that have a different collation to database?
Regards

Use
select * from INFORMATION_SCHEMA.tables
select * from INFORMATION_SCHEMA.columns
Petr

Collation conflict with Crystal Reports & a Primavera database

I'm new to Crystal Reports 2008 SP3; however, I'm ready to toss it out in relation to Primavera (version 7.0) data connectivity on my SQL Server - Windows 2008 R2 Standard (64-bit).
I have finally been able to establish a connection to the database (JDBC) - after struggling to get the right driver [sqljdbc.jar] on our SQL Server.
Now, I'm getting getting an error message relating to a COLLATION SETTING conflict:
'Failed to retrieve data from the database. Details: SQL Exception: [SQL State:] S0009 [Error Message:] Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AI" in the INTERSECT operation. [Database Vendor Code: 468]'
- Primavera version 7.0 default collation is SQL_Latin1_General_CP1_CI_AS
- I have searched the web for hints to resolving this error. Everything is pointing to the collation setting needing to be changed on the SQL Server.
__ Now, I'm checking on how to verify and change the collation setting on the SQL Server.
However, I'm suspecting that there is going to be another error around-the-corner.
It was my expectation & understanding that linking to various databases was a strong point for Crystal Reports. I have been working with another IT peer that is successfully using Crystal Reports for Remedy (HelpDesk application).
Has anyone experienced this situation? (any help is greatly appreciated)
Is there something (else) that is real obvious that I'm missing that would be ?

Don - Thanks for the feedback
I'm using JDBC bacuse I couldn't figure out how to use ODBC. The JDBC driver that I'm trying to use is: sqljdbc.jar which I downloaded last week (MS SQL Service JDBC Driver 3.0 ... version 3.0.1301.101 ... date published 04/20/2010). This driver (sqljdbc.jar) was added to the Classpath in CRConfig.xml.
I did install Fix Pack 3.3, my laptop has Windows XP Professional 32-bit - I have JAVA version 6 Update 14 as the enable version on my computer.
I don't understand when you say "use the MS SQL Server Native 10 as your driver" - I cannot find that by itself on the MS Download site. I keep getting 'MS SQL Server 2008 Feature Pack August 2008' to be downloaded. I'm guessing that this driver should already be loaded; however, I need to know the specific name to add to the Classpath in CRConfig.xml.
__ I found an article [SQL Server Natice Client 10.0 ODBC Driver] that stated the ODBC driver is contained in the file sqlncli10.dll
-- I searched my local harddrive (C:) and it is not found
-- Would this be stored on SQL server itself?
-- I'm guessing that I need to download the 'MS SQL Server 2008 Feature Pack' onto my lapttop
Still grabbing at the air...

Mssql collation conflict while update scom 2012 sp1 to r2

hi all
i have scom 2012 sp1 (windows server2008 r2), mssql 2012 sp1 (windows server2008 r2)
while updating scom 2012 sp1 to r2 error is appears:
"DB operations failed with SQL error 468: Cannot resolve the collation conflict between "Cyrillic_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation."
how can i change collation of db "OperationsManager" from "Cyrillic_General_CI_AS" to "SQL_Latin1_General_CP1_CI_AS"?
thanks in advance

For Failed to store data in the Data Warehouse. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation, you can refer below link
http://thoughtsonopsmgr.blogspot.com/2010/04/failed-to-store-data-in-data-warehouse.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

AlwaysOn & Contained Databases Collation Conflict

Here is my situation.
I have setup an alwaysOn availability group which is working fine.
In this AlwaysOn availability group I have converted the Adventureworks database to a contained database. I also added a Contained User.
Connecting to the secondary "Contained" database was no problem.
But here is my problem, when expanding the tables I received the following errormessage:"Cannot resolve collation conflict between "Latin1_General_CI_AS" and "Latin1_General_100_CI_AS_KS_WS_SC" in add operator occurring in SELECT statement
column 3."
Doing this action on the primary is no problem. Executing a select statement against the secondary is also no problem and returns a result.
After some trial and error, I’ve seem to fixed the issue by doing a failover to all my secondary databases.
After, expanding the tables to the primary & secondary worked.
Does anybody have an idea why this happened, and am I the only one experiencing this issue?
Thanks, Bram

Hi
Please refer to the link below:
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/02/26/sql-server-2012-partially-contained-databases-part-2-collation.aspx

IKM MSSQL Incremental Update fails on SQL Server 2000 - Collation Problem

I am having a problem where the the incremental update isn't cabable of updating the table it creates.
In the Flag Rows to Update I get the following error message:
446 : HY000 : java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Cannot resolve collation conflict for equal to operation.
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Cannot resolve collation conflict for equal to operation.
Source Code is:
update     S
set     IND_UPDATE = 'U'
from     SQRoracleStage..I$_tblOracleStage      S,
     SQRoracleStage..tblOracleStage      T
where     T.Occurance     = S.Occurance
and     T.PlanName     = S.PlanName
Oracle has suggested that the IKM be updated to include a COLLATE clause following the column name in the where clause.
update S
set IND_UPDATE = 'U'
from <%=snpRef.getTable("L", "INT_NAME", "A")%> S,
<%=snpRef.getTable("L", "TARG_NAME", "A")%> T
where <%=snpRef.getColList("", "T.[COL_NAME]\t= S.[COL_NAME] COLLATE replace_with_server_collation_string", "\nand\t", "", "UK")%>
However this code doesn't retrieve the collation string, but rather expects you to replace the replace_with_server_collation_sting with the value from the server.
Being unfamiliar with SQL Server I would have expected that the model should be capable of determining this value, and that the code should look something similar to:
update S
set IND_UPDATE = 'U'
from <%=snpRef.getTable("L", "INT_NAME", "A")%> S,
<%=snpRef.getTable("L", "TARG_NAME", "A")%> T
where <%=snpRef.getColList("", "T.[COL_NAME]\t= S.[COL_NAME] COLLATE <%=snpRef.getServerCollationString("L", "TARG_NAME", "A")%> ", "\nand\t", "", "UK")%>
It seems as though since ODI creates the table dynamically it should be capable of doing an update to it without intervention.
Has anyone found a work around for this issue?

I found the error :)
This is what happened:
I copied the tables from the MS SQL Server model to my Oracle model and then generated the DDL, so this gave me a quick set of tables in Oracle identical to the MS SQL database. But what I didn't know was that with the reverse engineer from MS SQL the ODI tool set the primary key columns to READ ONLY (and thus my copied tables also had read only primary key columns). Read only is OK for a source table but devastating for my tables I must load. So when I removed the read only indicator from the Oracle target table pk columns I was again a happy camper !
Thanks for being the one to talk to ! That really helped :)

Changing a column collation - problems?

Hello,
I have a VFP database that was migrated to SQL Server 2012. One of the VFP table's PK's utilized uppercase and lowercase values to distinguish rows, which of course does not fly by default in SQL Server.
Rather than having to redesign this part of the application and go through a data conversion, I'm thinking of changing the collation of this PK column and related FK fields to be case sensitive. On the surface it sounds like this would solve my
issue and the app would function as it always has.
Is there anything that would make me think twice about doing this?
Thanks.
Bill

Hi,
Be aware that changing collation at individual fields may break your queries.
Look at the following sample :
USE YourTestDB
SET NOCOUNT ON
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
SET ANSI_PADDING ON
CREATE TABLE tblX(X CHAR(10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, CONSTRAINT PK_tblX PRIMARY KEY CLUSTERED (X ASC))
CREATE TABLE tblY(Y CHAR(10) COLLATE Latin1_General_100_BIN NOT NULL, CONSTRAINT PK_tblY PRIMARY KEY CLUSTERED (Y ASC))
INSERT INTO tblX VALUES ('A');
INSERT INTO tblX VALUES ('B');
INSERT INTO tblX VALUES ('C');
INSERT INTO tblX VALUES ('D');
INSERT INTO tblX VALUES ('E');
INSERT INTO tblY VALUES ('A');
INSERT INTO tblY VALUES ('C');
INSERT INTO tblY VALUES ('E');
INSERT INTO tblY VALUES ('G');
INSERT INTO tblY VALUES ('I');
SELECT tblX.X, tblY.Y FROM tblX INNER JOIN tblY ON tblX.X = tblY.Y
-- Gives the following error
-- Msg 468, Level 16, State 9, Line 20
-- Cannot resolve the collation conflict between "Latin1_General_100_BIN" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
-- You'll have to rewrite your query as follows
SELECT tblX.X, tblY.Y FROM tblX INNER JOIN tblY ON tblX.X COLLATE Latin1_General_100_BIN = tblY.Y
-- Or
SELECT tblX.X, tblY.Y FROM tblX INNER JOIN tblY ON tblX.X = tblY.Y COLLATE SQL_Latin1_General_CP1_CI_AS
Sebastian Sajaroff Senior DBA Pharmacies Jean Coutu

Stored procedure - collation

Hi,
I managed to migrate a database from SQL2000 to SQL2012 but I have a problem with a stored procedure.
here ise the code :
USE [SMSPROD]
GO
/****** Object: StoredProcedure [dbo].[sms_received_104] Script Date: 16/03/2015 15:17:14 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
/****** Object: Stored Procedure dbo.sms_received_104 Script Date: 26/03/2008 22:11:24 ******/
/****** Object: Stored Procedure dbo.sms_received Script Date: 03/12/2007 9:36:09 ******/
ALTER procedure [dbo].[sms_received_104]
@jour int = 0,
@mois int = 0,
@annee int = 0
as
--declare @jour int, @mois int, @annee int,
declare @encodermail varchar(150), @advisermail varchar(100)
declare @date varchar(10), @msg varchar(70), @strCompany varchar(15), @stringsql VARCHAR(4000)
if @jour = 0 select @jour = day(getdate())
if @mois = 0 select @mois = month(getdate())
if @annee = 0 select @annee = year(getdate())
-- select @jour = day(getdate())
-- select @jour = 10
-- select @mois = month(getdate())
-- select @annee = year(getdate())
IF EXISTS(SELECT * FROM SMSPROD.dbo.vwSmsReceived WHERE (jour = @jour) and (mois = @mois) and (annee = @annee) AND (societe=104))
BEGIN
--SELECT @encodermail = 'DOE John' -- EasyCall 6834
--SELECT @encodermail = 'DOE John; SMITH Joe; Jane.doe@****.com' -- commented on 02/03/12
SELECT @advisermail = '[email protected]; [email protected]; [email protected]'
SELECT @advisermail = '[email protected]; [email protected]'
--SELECT @encodermail = 'TWIST Olivier'
--SELECT @advisermail = 'TWIST Olivier'
SELECT @stringsql = 'SELECT Dossier, ' +
'[Action - Actie], ' +
'[Téléphone - Telefoon Nr], ' +
'[Réponse - Antwoord], ' +
'[Message reçu le - Boodschap ontvangen op] ' +
'FROM SMSPROD.dbo.vwSmsReceived ' +
' WHERE(jour = ' +CONVERT(VARCHAR,@jour) + ') and (mois = ' +CONVERT(VARCHAR,@mois) + ') and (annee = ' +CONVERT(VARCHAR,@annee) + ')' */
SELECT @stringsql = '' +
'SELECT CHAR(13) + CHAR(10) + ''--- STOP SMS ---'' + CHAR(13) + CHAR(10) ' +
'SELECT Dossier
, [Réponse - Antwoord]
, [Message reçu le - Boodschap ontvangen op]
, [Téléphone - Telefoon Nr]
, [Action - Actie]
FROM SMSPROD.dbo.vwSmsReceived ' +
' WHERE (jour = ' + CONVERT(VARCHAR,@jour) + ') ' +
' AND (mois = ' + CONVERT(VARCHAR,@mois) + ') ' +
' AND (annee = ' + CONVERT(VARCHAR,@annee) + ') ' +
' AND (societe = 104) ' +
' AND ([Réponse - Antwoord] LIKE N''%stop%'' )' +
'SELECT CHAR(13) + CHAR(10) + ''--- OTHERS ANSWERS ---'' + CHAR(13) + CHAR(10) ' +
' SELECT Dossier
, [Réponse - Antwoord]
, [Message reçu le - Boodschap ontvangen op]
, [Téléphone - Telefoon Nr]
, [Action - Actie]
FROM SMSPROD.dbo.vwSmsReceived ' +
' WHERE (jour = ' + CONVERT(VARCHAR,@jour) + ') ' +
' AND (mois = ' + CONVERT(VARCHAR,@mois) + ') ' +
' AND (annee = ' + CONVERT(VARCHAR,@annee) + ') ' +
' AND (societe = 104) ' +
' AND ([Réponse - Antwoord] NOT LIKE N''%stop%'')'
--print @stringsql
--PRINT convert(varchar,LEN(@stringsql))
--return
SELECT @date = CONVERT(VARCHAR,@jour) + '/' + CONVERT(VARCHAR,@mois) + '/' + CONVERT(VARCHAR,@annee)
SELECT @msg = 'SMS responses received this ' + master.dbo.fct_string_date_dddd_d_MMMM_yyyy_hh_mm_ss( CONVERT(SMALLDATETIME,@date,103),'E')
-- SELECT @stringsql = 'EXEC master.dbo.xp_sendmail ' +
-- '@recipients = ' + CHAR(39) + @encodermail + CHAR(39) + ', ' +
-- '@copy_recipients = ' + CHAR(39) + @advisermail + CHAR(39) + ', ' +
-- '@body = ' + CHAR(39) + @msg + CHAR(39) + ', ' +
-- '@query = ' + CHAR(39) + @stringsql + CHAR(39) + ', ' +
-- '@subject = ' + CHAR(39) + @msg + CHAR(39) + ', ' +
-- '@attach_results = ''true'',' +
-- '@width = 500, ' +
-- '@no_header=''false'''
--print @stringsql
-- EXEC master.dbo.xp_sendmail @recipients = '', @copy_recipients = ';[email protected]', @message = 'SMS responses received this Monday 3 december 2007, 00:00:00', @query = 'SELECT * FROM SMSPROD.dbo.vwSmsReceived WHERE (jour = 3) and (mois = 12) and (annee = 2007)', @subject = 'SMS responses received this Monday 3 december 2007, 00:00:00', @attach_results = 'true',@width = 500, @no_header='false'
EXEC master.dbo.xp_sendmail @recipients = @encodermail, @copy_recipients = @advisermail, @message = @msg,
@query = @stringsql, @subject = @msg , @attach_results = 'true',@width = 500, @no_header='false'
END
And here is the reported error :
Msg 457, Level 16, State 1, Procedure sms_received_104, Line 69
Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved due to a collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "French_CI_AS" in add operator
Here is line 69
' AND (societe = 104) ' +
Both database are in "FRENCH_CI_AS" collation.
Can you help ?

There is a option (database_default) to force the collation of the columns.
https://social.msdn.microsoft.com/forums/sqlserver/en-US/695ecb2e-f2dc-4ced-a6c4-38527039b98f/database-collation-change

When / Where / If to change Collation

Greetings :)
I've been through the pain of upgrading sql 2000 databases to sql 2012 (via 2008r2) although the new box (sql2012) is not live yet.
I notice the COLLATION of the migrated user databases is SQL_Latin1_General_CP1_CI_AS and the server/system collation is Latin1_General_CI_AS.
QUESTIONS:
1) does it matter? they're almost the same
2) how would I have changed an individual databases (and contents) collation during the upgrade? (IE: backup / restore onto 2008r2 (autoupgrade), backup / restore onto 2012 (autoupgrade)).
I'm happy to go through the pain again if best.
3) wouldn't it now be easier to just change the server and system databases to match the upgraded user databases (SQL_Latin1_General_CP1_CI_AS)?
4) and wouldn't 3) above ensure continued smooth operations with the rest of the environment? (EG: Reporting Server)
Richard

Hi Richard,
Based on your description, SQL Server lets us store data in different collations, and we can set this at both the server level and at the individual database level. But when we join between different databases, or when we create a temp table and then
compare the temp table data to the data of a user database in a different collation, conflict may occurs.
When you restore a database, RESTORE uses the collation of the source database that is recorded in the backup file. The restored database has the same collation as the original database that is backed up. During the process of restoring database, you cannot
change the collation of the database. However, you can change the collation of the database(and contents) in SQL Server 2012 after restoring. You can create a script to change the collation of every object, and create a stored procedure to script all the objects
(primary keys, foreign keys, constraints, indexes), then run these scripts in SQL Server 2012. For more details, you can follow the steps in this blog:
Easy way to change collation of all database objects in SQL Server. Please make sure that you have backed up the database before changing the collation.
The server collation acts as the default collation for all system databases that are installed with the instance of SQL Server, and also any newly created user databases. The server collation is specified during SQL Server installation. Actually, it is a
complex operation to change the default collation for an instance of SQL Server, I recommend you not to change the server collation. For more details, please review this article:
Set or Change the Server Collation.
If you change the server collation to a new collation, the system databases (contains master, model, msdb and tempdb) will be rebuilt using the new collation setting. Any user modifications to these databases will be lost, so it is
important to backup any of this information you wish to retain.
Thanks,
Lydia Zhang

Error while updating SAINT SAPKINDA6B - Upgrade ECC 6.0

Hi SAP Experts.
I have a System SAP R/3 4.6 with Windows 2003 and SQL Server 2005.
I can´t updating the component PI to release 2004_1_46C.
The import was stopped, since an error occurred during the phase
IMPORT_PROPER, which the Support Package Manager is unable to resolve
without your input.
The following details help you to analyze the
problem: Error in phase: IMPORT_PROPER Reason for error:
TP_STEP_FAILUREReturn code: 0008 Error message: OCS Package ALL , tp
step "6", return
code 0008.
2EETP345 20:48:35: Retcode 1: SQL-error "468-Cannot resolve the
collation conflict between "SQL_Lat
2EETP345 in1_General_CP850_BIN2" and "SQL_Latin1_General_CP850_BIN" in
the equal to operation." in
2EETP345 DDL statement for "V_FLQSUM "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 20:48:35: error in DDL, nametab for "V_FLQSUM" not activated
Please, How can I solve the problem?.
Best regards.
Luis Gomez.

Check
Note 1019320 - sap_update_MSSDBSTATT Cannot resolve collation conflict
Markus

Connecting to MS SQL Server using ODI Agents

I'll start with an apology, since I'm sure it's something very obvious that I've missed. Other posts have similar, but I think slightly different issues - but they have helped me get this far.
We have ODI set up with two Agents (L and S running on Windows) which successfully connect to Oracle databases.
I'm trying to connect to our first MS SQL Server database, and while a test through "Local (No Agent)" is successful, the connection is not successful when I try through one of the agents.
This is true both when I test through Topology Manager on my laptop and when I use the ODI Topology Manager on the server running the agents themselves.
In attempting to fix the problem, I have updated/checked as follows:
Downloaded updated MS SQL Server drivers (I'm connecting to a MS SQL Server 2005 database). The new MS driver is version 3.0 and I've copied file sqljdbc4.jar to the ODI home drivers directory on both my laptop and on the server which runs the agents.
Checked that we have a newer JRE installed - we have JRE 6 update 7 installed (1.6.0.17_b04) on the server which runs the agents.
Updated the ODI_JAVA_HOME environmental variable so that it points to the jre6 directory on the server which runs the agents.
Stopped and restarted the Agent services.
Closed and reopened Topology Manager.
Configured the SQL Server data server to use the following JDBC driver:
com.microsoft.sqlserver.jdbc.SQLServerDriver
Configured the JDBC url as follows (changing the hostname):
jdbc:sqlserver://<hostname>:1433;selectMethod=cursor;integratedSecurity=false
Tested using 'Local (No Agent)' successfully.
Tested through an agent and received the following error:
java.lang.Exception:
     at com.sunopsis.graphical.c.po.a(po.java)
     at com.sunopsis.graphical.c.po.t(po.java)
     at com.sunopsis.graphical.c.po.g(po.java)
     at com.sunopsis.graphical.c.po.a(po.java)
     at com.sunopsis.graphical.c.po.a(po.java)
     at com.sunopsis.graphical.c.ja.actionPerformed(ja.java)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.Dialog$1.run(Unknown Source)
     at java.awt.Dialog$3.run(Unknown Source)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.awt.Dialog.show(Unknown Source)
     at java.awt.Component.show(Unknown Source)
     at java.awt.Component.setVisible(Unknown Source)
     at java.awt.Window.setVisible(Unknown Source)
     at java.awt.Dialog.setVisible(Unknown Source)
     at com.sunopsis.graphical.c.po.r(po.java)
     at com.sunopsis.graphical.c.po.<init>(po.java)
     at com.sunopsis.graphical.frame.b.jh.by(jh.java)
     at com.sunopsis.graphical.frame.bo.x(bo.java)
     at com.sunopsis.graphical.frame.bo.d(bo.java)
     at com.sunopsis.graphical.frame.w.actionPerformed(w.java)
     at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
     at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
     at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.processMouseEvent(Unknown Source)
     at java.awt.Component.processEvent(Unknown Source)
     at java.awt.Container.processEvent(Unknown Source)
     at java.awt.Component.dispatchEventImpl(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
     at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
     at java.awt.Container.dispatchEventImpl(Unknown Source)
     at java.awt.Window.dispatchEventImpl(Unknown Source)
     at java.awt.Component.dispatchEvent(Unknown Source)
     at java.awt.EventQueue.dispatchEvent(Unknown Source)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
     at java.awt.EventDispatchThread.run(Unknown Source)
I'm sure it's something obvious that I've missed, but I've now spent close to two days researching, testing and drinking too much coffee. Any help would be very gratefully received!
Thanks.

After more investigation and even more chocolate, we've identified the problem and it's now working. For anyone else who strikes this problem in future, here's something to check/consider/try:
Even though Squirrel SQL Client was connecting and working ok using the MS JDBC driver (v 3.0), it recorded this in its logs:
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the INTERSECT operation.
We've found that the open source jTDS driver does not have the same issue as the Microsoft one.
We've installed the current jTDS driver, recorded the driver name (net.sourceforge.jtds.jdbc.Driver) and the JDBC URL (jdbc:jtds:sqlserver://<hostname>:1433/<database>) and the connection is now working fine.
Hope this helps other people...
Thanks to those of you who offered suggestions and things to check...much appreciated.
Robyn

Error in SQL Procedure

Hi Experts
I have created following procedure which is showing Run Time error
alter proc Stock_item
as
begin
          create table #temp
          main_Group varchar (40),
          intermediate_group     varchar(40),
          final_Group          varchar,
          item_code varchar(20),
          item_name varchar (50),
          Qty numeric(10,3)
          insert into #temp (item_code, item_name, Qty)
          select itemcode , itemname, onhand from OITM
          update tmp set tmp.main_Group = 'Raw material'
          from OITM T1 , #temp tmp
          where T1.QryGroup1 = 'Y' and T1.Itemcode = tmp.item_code
          select * from #temp
end
Error Message is : Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP850_CI_AS" in the equal to operation.
Msg 468, Level 16, State 9, Procedure Stock_item, Line 26
Plz check and tell me what can be reason
Regards
Gorge

Hi Gorge,
Try the following:
create table #temp
main_Group varchar (40),
intermediate_group varchar(40),
final_Group varchar,
item_code varchar(20) COLLATE SQL_Latin1_General_CP850_CI_AS,
item_name varchar (50),
Qty numeric(10,3)
Regards,
Andrew.

How can I get this query to work?

HI
SELECT TOP 200 [word] ,COUNT(word) AS count
          FROM [COMMENT_WORDS]
          where word NOT in (SELECT wordText FROM word)
            GROUP BY word
            ORDER BY COUNT desc
gives me this error:
Msg 468, Level 16, State 9, Line 1
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
please help

Thanks I changed the count name but I am still getting
Msg 468, Level 16, State 9, Line 1
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
I also went into the word database and ran
    ALTER DATABASE [word] COLLATE
    Latin1_General_CI_AS
and now both databases have the same colaltion but I still get the error:
Msg 468, Level 16, State 9, Line 1
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
I am using ms sql 2005

Collation conflict

Similar Messages

Maybe you are looking for