Database Design Checklist - SQLServerCentral Forums
Database Design Checklist - SQLServerCentral Forums
Menu
Home Forums SQL Server 2005 SQL Server 2005 General Discussion Database Design
Checklist
Chandhini
Ten Centuries
Points: 1243
More actions
July 16, 2009 at 6:20 am #133965
can anyone give me the database design checklist to make sure the database design is proper?
like,
5. Is Database normalized?
Thanks,
https://www.sqlservercentral.com/forums/topic/database-design-checklist 1/5
11/22/21, 7:35 PM Database Design Checklist – SQLServerCentral Forums
Ramani
Grant Fritchey
SSC Guru
Points: 397386
More actions
July 16, 2009 at 7:44 am Unlike #1025645
I'd add a step to design the clustered indexes. They should be part of the fundamental
decisions around the database design.
----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and
sweat and blood...
Theodore Roosevelt
Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution
Plans, 3rd Edition
Product Evangelist for Red Gate Software
Chandhini
Ten Centuries
Points: 1243
More actions
July 16, 2009 at 11:41 pm Unlike #1026015
https://www.sqlservercentral.com/forums/topic/database-design-checklist 2/5
11/22/21, 7:35 PM Database Design Checklist – SQLServerCentral Forums
Grant, when constraints are defined, clustered index also will come (for primary key). or
anything else apart from constraints, should that be defined?
Regards,
Ramani
Grant Fritchey
SSC Guru
Points: 397386
More actions
July 17, 2009 at 6:01 am Unlike #1026112
Well, the reason I'm suggesting you need to define the clustered index as a seperate step is
because, it doesn't necessarily come from the primary key. Don't confuse the two because SQL
Server defaults to making the primary key clustered. One doesn't automatically flow from the
other. I like to examine the structures and make a conscience decision as to where I'll place the
clustered index. More often than not, it's on the PK, but not always.
Since the data is stored with the clustered index, it makes sense to use the most common
access path to the data as the cluster. In a lot of tables the most common access path is the
PK. But in some tables it might be through foriegn keys, say a child table that is only accessed
through joins to the parent, or by specific date ranges, who knows. Understanding the design
such that you can determine these access paths up front should be standard part of the design,
in my opinion anyway.
----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and
sweat and blood...
Theodore Roosevelt
Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution
Plans, 3rd Edition
Product Evangelist for Red Gate Software
https://www.sqlservercentral.com/forums/topic/database-design-checklist 3/5
11/22/21, 7:35 PM Database Design Checklist – SQLServerCentral Forums
Chandhini
Ten Centuries
Points: 1243
More actions
July 17, 2009 at 7:21 am Unlike #1026166
Now i understood y we need to include one more item for defining clustered index.
Regards,
Ramani
You must be logged in to reply to this topic. Login to reply
https://www.sqlservercentral.com/forums/topic/database-design-checklist 4/5
11/22/21, 7:35 PM Database Design Checklist – SQLServerCentral Forums
https://www.sqlservercentral.com/forums/topic/database-design-checklist 5/5