Sorry, but I dont know the specifics. I am not a “sql expert” (I can barely spell SQL… hahah), but have heard that we did make it so it worked like the Old Progress server worked.
I just did a search in Google and asked AI… here is what I got: Maybe someone else who IS a SQL expert may know more about this and where it is located.
@kananga perhaps
Case sensitivity is one part of SQL collation that’s going on under the collation umbrella that needs planning and consideration during the database design stage.
Collation and Unicode Support - SQL Server | Microsoft Learn
Collation values are easiest to find by right clicking at the database in SSMS and checking ‘properties’. They’re stored on sys.databases and sys.servers if you’re checking from code or an editor.
If SQL collation at the data’s scope is case insensitive, then “THING” and “thing” will be considered to be equivalent or duplicate values. But that outcome depends on other context. If a column doesn’t have a DISTINCT constraint or isn’t PRIMARY KEY, it will concurrently contain the values “THING” and “thing” without any complaint. Case collation only modifies a behavior of those constraints, it doesn’t apply a constraint by itself.
If a field depends on code to manage distinctness, then distinctness is fragile and can break.
Brilliant, he’s cracked it. Why stop at capitals? Let’s make the database sing while we’re at it.
I was referring to this for context… Pff…
