Help get this topic noticed by sharing it on Twitter, Facebook, or email.

DBAmp Collation types

When we set up DBAmp, we asked our DBA to set up our SQLServer as Case Sensitive. In doing this as I started creating our integration queries and tables, I have run across error: Lookup Error - SQL Server Database Error: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP1_CS_AS" in the equal to operation. So I had our DBA enter the Collation Name on the Oracle Linked server to SQL_Latin1_General_CP1_CS_AS (collation compatible = true).

Is this the best practice? The reason we are asking is because, the errors are on the field type and not the data.
1 person has
this question
  • The linked server is always in the server collation, not the database collation.

    The error message is telling you that it will have trouble comparing data from the linked server in the server collation with data in the database in the database collation if those collations are different.

    Most customers have the server collation as case insensitive and have let the database collation default to match that.
  • (some HTML allowed)
    How does this make you feel?
    Add Image

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned