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,739 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,757 reads
2014-11-04 (first published: 2014-10-06)
1,385 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,726 reads
A RAG pipeline that answers questions in the demo is not the same thing...
By Steve Jones
“A multitude of bad ideas is necessary for one good idea” – from Excellent...
Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your...
Comments posted to this topic are about the item Looking for New Blood
Comments posted to this topic are about the item Server-Level Row Counts for Tables...
Comments posted to this topic are about the item Parameter Sensitive Plan Optimization vs....
What types of secondary replicas are available for the Azure SQL Database Hyperscale edition?
See possible answers