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,635 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,718 reads
2014-11-04 (first published: 2014-10-06)
1,335 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,677 reads
On May 8, 2025, we hosted our first official event in Switzerland at Prime...
By Steve Jones
Tomorrow is the Redgate DevOps Day in Atlanta. You can still sign up, so...
By Kevin3NF
Too many IT teams run index rebuild jobs on autopilot. Every night. Every index....
Comments posted to this topic are about the item Are Data Breaches Inevitable?
Comments posted to this topic are about the item The Internals of Writing a...
Comments posted to this topic are about the item How to Safely Remove a...
In SQL Server, when the buffer manager write pages to disk, page protection is added to the pages. There are two types of protection: torn page protection and checksum page protection. What happens with regards to concurrency with page protection during writes?
See possible answers