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,684 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,726 reads
2014-11-04 (first published: 2014-10-06)
1,365 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
I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...
By Steve Jones
I’m in the UK today, having arrived this morning in London. Hopefully, by this...
I’m not trying to start up a debate whether you should use tabs or...
I have a script task that tries to execute a HTTP request, which seems...
Comments posted to this topic are about the item SQL Server 2025 Standard Developer...
Comments posted to this topic are about the item URL Safe or Not?
If I use BASE4_ENCODE() in SQL Server 2025, is the output URL Safe by default?
See possible answers