How do you handle case sensitivity issues across databases?

Answered

DSP User

• October 30, 2017 16:38

The topic of case sensitivity has come up at a client (Pharma Industry). The DSP application runs on a non-case sensitive database and both the clients source and target systems run on case sensitive databases. This quite often manifests as a problem when extracting data due to primary key violations. I am able to provide consultants with ways of working to deal with known values that are case sensitive to ensure that value mapping and target validation check work OK. However, I am looking for advice/guidance on how consultants have handled this topic with their clients to allay their concerns about any risks this poses to the migration process. Any guidance will be greatly appreciated. Andy

1

• Best answer

  

  DSP Expert

  • October 30, 2017 16:52

  KVandergriend: For case sensitive keys, the column collation should be changed manually to SQL_Latin1_General_CP1_CS_AS. This will prevent errors on refresh. You will also want to prevent the tables from being rebuilt by changing the Package Type to Manual CranPort. It is rare where the non-primary key fields are case sensitive, but those could also be changed manually.

  0

Please sign in to leave a comment.