I thought my database was collation agnostic
My struggles with a customer's database that used a different collation sequence. The easy way is never the right way, or is it?
2018-06-08 (first published: 2016-01-14)
4,550 reads
My struggles with a customer's database that used a different collation sequence. The easy way is never the right way, or is it?
2018-06-08 (first published: 2016-01-14)
4,550 reads
After having seen many systems that use GUIDs as the primary key for every table, it is time to say enough is enough.
2014-12-18
9,967 reads
By Steve Jones
If someone is trying to convince you it’s not a pyramid scheme, it’s a...
By Steve Jones
I was looking back at my year and decided to see if SQL Prompt...
In the era of cloud-native applications, Kubernetes has become the default standard platform for...
Hi experts, I have a 3+ TB database on a 2019 sql server which...
Comments posted to this topic are about the item The North Star for the...
Comments posted to this topic are about the item Multiple Escape Characters
In SQL Server 2025, I run this code (in a database with the appropriate collation):
SELECT UNISTR('%*3041%*308A%*304C%*3068 and good night', '%*') AS 'A Classic';
What is returned? See possible answers