Jeff Reinhard


SQLServerCentral Article

A Pattern for Email Address storage and retrieval

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.

4.39 (33)

You rated this post out of 5. Change rating

2017-09-15 (first published: )

8,657 reads

Blogs

SQL Saturday Baton Rouge 2025

By

SQL Saturday Baton Rouge is a great event hosted on LSU’s campus that has...

Responsible AI: Why Leaders Need More Than Just Guardrails

By

In the rush to adopt artificial intelligence, many organizations have quickly built ethical frameworks,...

TempDB Performance Tuning in SQL Server 2022 vs 2016 vs 2019

By

📘 What Is TempDB and Why It Matters TempDB is a shared system database in SQL...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

When DBAs Should Consider Using SQL Server to Store Vector Data and If It Makes Sense

By dbakevlar

Comments posted to this topic are about the item When DBAs Should Consider Using...

Row Count task in data flow fails with "unspecified error"

By Gergely Mészáros

Hi all, I have a data flow task with: Flat File Source (csv) ->...

Visit the forum

Question of the Day

Capacity Planning for an Existing SQL Server Workload?

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