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,547 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,710 reads
2014-11-04 (first published: 2014-10-06)
1,308 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,659 reads
By Steve Jones
Next week is the 2024 PASS Data Community Summit in Seattle. I’ll be traveling...
By Steve Jones
bye-over – n. the sheepish casual vibe between two people who’ve shred an emotional...
I’m hosting a free webinar at MSSQLTips.com at the 19th of December 2024, 6PM...
Comments posted to this topic are about the item PASS Summit Time
I have a backup of full, differential and transaction log setup for our database....
Hello everyone, I hope you can help me. I have a table with measurement...
I have run this on SQL Server 2022 for the Sales database:
ALTER DATABASE Sales SET AUTO_CREATE_STATISTICS ON (INCREMENTAL = ON)I then run this in the Sales database:
USE Sales GO CREATE STATISTICS CustomerStats1 ON dbo.Customer (CustomerKey, EmailAddress) WITH INCREMENTAL = OFFThe dbo.Customer table is partitioned. How are statistics created? See possible answers