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,690 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,730 reads
2014-11-04 (first published: 2014-10-06)
1,366 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,700 reads
By Steve Jones
on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...
By DataOnWheels
I have been active in the data community throughout my career. I have met...
By Vinay Thakur
Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...
SQL Server is typically viewed as a transactional or analytical database engine. However, it...
Hello, Is there a way in Azure SQL Database to change the 'Blocking Process...
Comments posted to this topic are about the item Having a Little Fun at...
On SQL Server 2025, when I run this, what is returned?
SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL') See possible answers