Email addresses are very prevalent in IT systems and often used as a natural primary key. The repetitive storage of email addresses in multiple tables is a bad design choice. Following is a design pattern to store email addresses in a single table and to retrieve them efficiently.
2017-09-15 (first published: 2015-09-24)
8,722 reads
A brief introduction to the sparse option and script to help decide when to use it
2016-08-25 (first published: 2015-04-10)
1,739 reads
2014-11-04 (first published: 2014-10-06)
1,374 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,703 reads
By Steve Jones
If you’ve wanted a SQL Server MCP server for your databases, it’s available. The...
Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...
By DataOnWheels
I have been asked many times about how the name “Data on Wheels” came...
Comments posted to this topic are about the item Make It Routine
Comments posted to this topic are about the item DBCC CHECKDB Limits III
Comments posted to this topic are about the item CROSS APPLY Fundamentals: Part 1
On SQL Server 2025, does DBCC CHECKDB support Memory-Optimized tables?
See possible answers