Beware of big green dragons, er, well, of unexpected changes when changing a column's datatype. You might be unpleasantly surprised! 🙀 Beware!
An in-depth analysis of the new native UTF-8 support in SQL Server 2019.
Demystifying What "sqlservr -q" Actually Does (last updated: 2019-01-07 @ 02:25 EST / 2019-01-07 @ 07:45 UTC ) For various reasons, people sometimes find themselves in the unfortunate (and unenviable) situation of having an Instance of SQL Server configured with the wrong Collation. This can often lead to unexpected errors and/or sorting and comparison behavior.… Continue reading Changing the Collation of the Instance, the Databases, and All Columns in All User Databases: What Could Possibly Go Wrong?
Come see the complete set of rules governing how you name things in SQL Server
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 😺).
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
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