The Uni-Code: The Search for the True List of Valid Characters for T-SQL Identifiers, Part 3 of 2 (Delimited Identifiers)

The investigation into valid T-SQL identifier characters continues. Apparently I was not done.

What’s in a Name?: Inside the Wacky World of T-SQL Identifiers

Come see the complete set of rules governing how you name things in SQL Server

Which Collation is Used to Convert NVARCHAR to VARCHAR in a WHERE Condition? (Part B of 2: “Rabbit”)

Who will win "Who's Collation is it Anyway?" Database Collation is ahead, but Column Collation isn't about to give up.

Which Collation is Used to Convert NVARCHAR to VARCHAR in a WHERE Condition? (Part A of 2: “Duck”)

Microsoft says string literals not prefixed with "N" are converted to the Code Page of the Database OR referenced column. Is that true?

All New Collations in SQL Server 2017 Implicitly Support Supplementary Characters

SQL Server 2017 adds 68 new Collations, but none end with "_SC". This seems to be due to Supplementary Characters being supported by default (which is great 😺).

No, Binary Collations are not Case-Sensitive

Quite often people will use, or will recommend using, a binary Collation (one ending in "_BIN" or "_BIN2") when wanting to do a case-sensitive operation. While in many cases it appears to behave as expected, it is best to not use a binary Collation for this purpose. The problem with using binary Collations to achieve… Continue reading No, Binary Collations are not Case-Sensitive

Impact on Indexes When Mixing VARCHAR and NVARCHAR Types

You may have heard, or read, that you should not mix VARCHAR and NVARCHAR datatypes, especially when one of them is a JOIN or WHERE predicate / condition, as doing so will invalidate indexes. While it is always best to have all datatypes be the same for a particular operation (comparison, concatenation, etc), the actual… Continue reading Impact on Indexes When Mixing VARCHAR and NVARCHAR Types