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,524 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,524 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,918 reads
By John
In a recent video, I took a hands-on look at the Next Gen General...
By Rohit Garg
India’s 2025 tax reforms have introduced a bold shift in how income is taxed,...
In today’s Software Development Life Cycle (SDLC), having a robust build pipeline is very...
We are in the process of upgrading to SQL Server 2022 and would like...
Comments posted to this topic are about the item How to Choose the Right...
Comments posted to this topic are about the item Adding Defaults
I have a table, called dbo.logger, in SQL Server 2022. I decide to add two new columns to this table with this code.
ALTER TABLE dbo.logger ADD CreateDate DATETIME CONSTRAINT dfGetDate DEFAULT GETDATE() GO ALTER TABLE dbo.logger ADD ModifyDate DATETIME DEFAULT dfGetDate GOWhat happens when I run these two batches? See possible answers