HQ and Store Collation - HQ Client complains

May 30, 2007 5 Replies
C

Hi there, we have a serious issue here. I upgraded several shops accross europe to V1.3.1006 and SQL Server 2005. I used the 1.3 refresh for that. In germany and the netherlands everything went fine and we can use the HQ Client to send the data to the german and dutch HQ databases. In France, Switzerland and Spain however the HQClient stops in the middle of the WS 250 saying that the database collations are different although i checked both collations and they are the same (as far as Store Op Admin, HQ Admin and Server Management Studio says). Any ideas?



Chris



Vote
Twitter Facebook LinkedIn
M

You may have the correct collation for the whole database, but every field of every table has its collation. Anyway check every field in the item table and sure that it has the correct collation.

Sp_help ITEM

"Christian Olsen" wrote in message news: snipped-for-privacy@microsoft.com...

Vote
Twitter Facebook LinkedIn
M

Sorry,

when you run Sp_help ITEM, you will have null values in the collation field which means "default database collation"

thanks,

Vote
Twitter Facebook LinkedIn
C

Hello Mahmoud,

thanks for your quick reply. Do you mean I have to check every field of the storedatabase against the serverdatabase? If so: is there a table where the field-related collations are stored so that I can compare them usin SQL?

Chris

"Mahmoud Am> Sorry,

Vote
Twitter Facebook LinkedIn
M

Hi Christian, As you mentioned that the connection is working fine in some sites, so you have to check sites (store database) that is not connected, and the connection is stopped in WS250 "Inventory Items" that is related to Item table, so (query is: sp_help item) will query the item table and give you the information about every field in that table. note that null values refering to "database default collation"

hope this helpful..

"Christian Olsen" wrote in message news: snipped-for-privacy@microsoft.com...

Vote
Twitter Facebook LinkedIn
C

Sorry, that was my mistake. The error occurs in the WS401 It says the collation error occured during:

SELECT #UpdateWorksheet_DataUpload_LocalCustomers.* FRUM #Upd

noth> Hi Christian,

Vote
Twitter Facebook LinkedIn

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required