SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Database Design Checklist


Database Design Checklist

Author
Message
Chandhini
Chandhini
SSC Journeyman
SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)

Group: General Forum Members
Points: 91 Visits: 211
can anyone give me the database design checklist to make sure the database design is proper?
like,
1. Have db design met the the requirement specification?
2. Is concentual Design created?
3. Is logical Design created?
4. Is Physical Design created?
5. Is Database normalized?
6. Are constraints defined?

please suggest me any other points are to be inserted?.


Thanks,
Ramani
Grant Fritchey
Grant Fritchey
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41271 Visits: 32666
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

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
Chandhini
Chandhini
SSC Journeyman
SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)

Group: General Forum Members
Points: 91 Visits: 211
Thanks for the suggestion.

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
Grant Fritchey
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41271 Visits: 32666
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

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
Chandhini
Chandhini
SSC Journeyman
SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)SSC Journeyman (91 reputation)

Group: General Forum Members
Points: 91 Visits: 211
Thanks a lot for this clarification Grant.

Now i understood y we need to include one more item for defining clustered index.


Regards,
Ramani
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search