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,657 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,344 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,685 reads
By DataOnWheels
SQL Saturday Baton Rouge is a great event hosted on LSU’s campus that has...
By Chris Yates
In the rush to adopt artificial intelligence, many organizations have quickly built ethical frameworks,...
By Rohit Garg
What Is TempDB and Why It Matters TempDB is a shared system database in SQL...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item When DBAs Should Consider Using...
Hi all, I have a data flow task with: Flat File Source (csv) ->...
You're tasked with planning capacity for a new SQL Server database workload. Which of the following is the most accurate way to determine how much CPU, memory, and I/O throughput your workload requires? What single or multiple tools would you use to answer the questions around resource needs?
See possible answers