Migrating from ASE to SQL Server, our embedded SQL in C# assumes case insensitivity. How can I enforce it globally without updating each query? For instance:
WHERE user_key COLLATE SQL_Latin1_General_CP1_CI_AS = :userParam
hey, i’ve been testing updtaing the server collation but it gets a bit wonky sometimes. has any1 noticed odd query plans or other issues? curious abt how it interacts with your setup. what do u reckon?
hey, maybe you could test a global settings change in a staging deploy. it saved me tons of query adjustments, but be careful re: indexing quirks. sometimes a few tweaks here and there can be easier than a full database overhaul.
hey, you can change the default collation at the db level to force ci, no need to update each qry. have you playd around with that option yet? would be interessting to hear if anyone faced any hiccups with such a global change.
hey, you might try configuring the instance level collation, but be awere it can affect indexing. test it in a staging setup before rollout. cheers!
Based on my experience, setting the default collation at the time of database creation is the most effective solution. This approach ensures that all queries automatically inherit case-insensitive behavior without the need for individual modifications. If altering an existing database, it is crucial to perform thorough testing in a controlled environment to avoid unexpected issues like changes in index performance or query plans. Meticulous planning and validation are key to seamlessly enforcing case insensitivity across your SQL Server deployment.