
CTL10.04.001
Revision 11/10/2009 A
SQL Server 2008
Database Design
CRITICAL TASK LIST PROGRAM
This document contains steps that will assist you in designing a database for SQL Server 2008 RTM Enterprise Edition (non-clustered) operations. It defines the basic steps for creating a database design, and should be used as a starting point.
Review each item, placing a check in the “Confirmed” column when the task line is complete. Any line not marked “Confirmed” should stop the process until you have completed that line item.
This CTL is not meant to be a replacement for the official documentation from the product manufacturer.
CTL NUMBER
This Critical Task List is identified by a CTL number in the upper right-hand side of this document. You should use the latest CTL (identified by the date and an alpha-numeric code.
HOW TO BE ASSURED OF HAVING LATEST DATA
You can add additional information to this checklist based on your organization’s need.
CONTENT
Critical Task List 10.04.001 contains steps required to create a good database design on a SQL Server 2OO8 system. Other system and environmental factors will dictate changes to this CTL as well as additional steps that you should follow for your database design tasks.
All content is the sole responsibility of the server owner; Microsoft Corporate provides no warranties implied or implicit in this document. This document is not a product of the Microsoft Corporation.
SUPPLEMENTS
Official Site Link: http://www.simple-talk.com/author/buck-woody/
Whenever you receive a supplement affecting your checklist, write in the appropriate information. Printed replacement checklist pages will be made available to you as quickly as possible. A notation on the bottom inside corner of these pages will indicate that they reflect certain supplements.
COMMENTS AND QUESTIONS
Comments and questions should be directed through buck.woody@microsoft.com.
Critical Task Lists Managers
Buck Woody “Real World DBA”(MSFT U.S.).
Task |
References |
Confirmed |
Obtained Business Requirements from submitting organization |
||
Developed further questions from Business Requirements. |
||
Submitted questions to originator and received responses. |
||
Meeting held with development and organization team to agree on final requirements. |
||
Nouns decomposed from finalized Business Requirements document. |
||
Nouns grouped into logical entities. |
||
Verbs Decomposed from finalized Business Requirements document. |
||
Initial logical Entity Relationship Diagram (ERD) created. |
||
Logical ERD developed into 3rd Normal Form (3NF). |
||
Data Types Determined for each entity. |
||
Primary and Foreign Keys defined. |
||
Unique and other constraints defined from finalized Business Requirements document. |
||
Security plan developed from finalized Business Requirements document. |
||
Physical design created from finalized ERD. |
||
File Storage choices created and finalized. |
||
Finalized design tested with top-20 queries from each entity. |
Load comments