Collation error

  • A system I support is having a very odd collation error.  The system is deployed to several centers across the country and canada, with each center running a local copy of the database using MSDE.  In only one center (located) in Canada, we are getting an error indicating an issue with collation settings.  The default collation for the database is  SQL_Latin1_General_CP1_CI_AS as were all the columns that had an explicit collation.  If I change the columns (by updating collationid in syscolumns) to reflect a collation of Latin1_General_CI_AS, the collation errors go away only to replace by collation errors in other parts of the application.  It is important to note that we do have a few stored procedures that create temp tables and explicitly define a collation of SQL_Latin1_General_CP1_CI_AS  for some columns.  So I am not surprised that setting collations to Latin1_General_CI_AS does not solve the problem.  Initially we thought that perhaps the default collation of the database was incorrect, but it isn't.

    Any thoughts anyone?

    Gordon Pollokoff

    "Wile E. is my reality, Bugs Bunny is my goal" - Chuck Jones

  • check the collation of the tempdb.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply