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,651 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,721 reads
2014-11-04 (first published: 2014-10-06)
1,341 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,683 reads
By Steve Jones
The PASS Summit goes on tour this year, with a September stop in Dallas....
By Kevin3NF
Settings That Could Be Hurting Your Performance If you’ve ever created a new SQL...
I needed to run a PowerShell cmdlet in an Azure Devops pipeline. The cmdlet...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Hi, Would it be possible to upgrade from sql server 2012 sp4 to sql...
Comments posted to this topic are about the item Has the PK been used...
You're analyzing a query execution plan in SQL Server to determine whether the query optimizer chose to use a primary key index. Which Dynamic Management View (DMV) would you use to verify the usage of the primary key in the plan?
See possible answers