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,719 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,738 reads
2014-11-04 (first published: 2014-10-06)
1,373 reads
Data Compression and Snapshot Isolation don't play well together, you may not see a performance benefit
2014-10-02
3,701 reads
By Steve Jones
This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...
The DBA life is fraught with pain. Those battles that we endure are mostly...
Every PostgreSQL migration eventually hits the same fork in the road. The database is...
WA:08218154393 nomor 275 Blok 4, Jl. Raya Uluwatu dan 5 No.99, Ungasan, Kec. Kuta...
WA:08218154393 Jl. Raya Ubud No.10, Petulu, Kecamatan Ubud, Kabupaten Gianyar, Bali 80571
WA:08218154393 Jl. Suwung Batan Kendal No.2, Sesetan, Denpasar Selatan, Kota Denpasar, Bali 80222
Can I set Accelerated Database Recovery on tempdb?
See possible answers