SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 120 of 365 Next >

In the last few articles in this series, I’ve explained the process to develop a database design in an intelligent, systematic way. I've covered the process for gathering business requirements, the conversion of those requirements into logical statements, the creation of entities, attributes and relationships, and the creation of the logical Entity Relationship Diagram (ERD) — a graphical tool showing this logical design.

The example database I’m designing tracks the hours consultants spend on projects. I've been careful to design the entities and attributes in accordance with the requirements document — in fact, making sure the requirements reflect the data, rules and processes for the system forms the basis of everything else I’ll show you in this process. It’s the single-most important step.

After the initial design, I explained a problem with the relationship aspect of the diagram. I had to go back to the design committee for clarification, and once I did, I altered the design to properly reflect the relationship. While I was at it, I added a few attributes that were missing.

This design is what is delivered to the business community, along with the business rules, user documentation and so forth, in the form of that graphical Entity Relationship Diagram. That serves as a discussion vehicle, something that has simple symbols and text to rapidly convey what information the database will store, and the rules that will be enforced for optionality (whether something can, should or must exist) and cardinality (how data is related to each other). Once all of the teams agree on the logical layout of the data, the next step is to turn that diagram into a physical model for whatever platform the organization will use. In this series, I’ll use SQL Server, but if you pick another database system such as Oracle or XML files, the diagram will look different. This is the reason for separating the logical ERD from the physical design — it allows the business and developers to create a program that can be implemented on multiple platforms, and the data professionals to focus on the best way to implement the actual platform in the most secure, best performing method.

The business community normally doesn't have much use for the physical ERD I’ll make next. That deliverable is used more by the database analysts, administrators and developers. Not every shop uses a graphical ERD for a physical model. In some cases you’ll go straight from the logical ERD graphic to Transact-SQL statements, and that’s OK. If I’m using an expensive tool for the data design, it often has the capability to simply add an option to show either the logical or physical ERD. I find that the larger the project, the more graphics I use, since I often need to coordinate with more people.

There are several ways to convert a logical design to a physical implementation, but the route I usually use looks something like this:

Apply first normal form rules to the logical ERD

Convert the entities into tables
Convert the attributes into fields
Create primary keys

Apply second normal form rules to the logical ERD

Create foreign keys

Enforce business rules with constraints and defaults
Apply third normal form rules to the logical ERD
Add any platform components

While this might look like a short list, it's longer than you might think. Let's try it out, one step at a time.

Apply first normal form rules to the logical ERD

Recall that first normal form specifies separating out any repeating entities into multiple entities.

Convert the entities into tables

The logical model I have largely fits this rule, so the first part of the process is complete.

Convert the attributes into fields

So far, the logical diagram holds — with a couple of small changes. For one, I’ll change any spaces in words to underlines. While SQL Server allows spaces in the names of many objects, I’d have to bracket [ ] them when I reference them in any T-SQL statements. That's inviting an error, and I would like to avoid errors where possible.

I’ve also changed the singular notation on the entities to plural. While this seems a minor change, people can get really concerned about it. My personal rule of thumb is that when I designing logical entities, I'm describing a concept. Therefore, Client is a singular entity, so I keep it singular. Hours and Skills don't stand alone, so those entities I keep plural. When I convert the logical entities to physical tables, I'm no longer describing concepts, but buckets. For that reason, I’ll stick with naming the tables in the plural. There are other schools of thought on this, but in the end the key is to be understandable and consistent.

I’m not done with the fields just yet, though. The other part of this process I’ll have to complete is setting data types, nullability and so on. I’ll complete that in a bit.

Create primary keys

At this point I’ll add my primary keys. In another article on this site I discussed primary keys at length, but for my purposes here I'll simplify the process for creating a primary key into just one rule:

Set a primary key that completely identifies each row in the table in a unique way.

It's a simple rule, and yet its application is a bit more complex. As you may recall from the earlier tutorial regarding keys, there are two possibilities. The first is that a current attribute fits the bill. This is called a "natural" key. In my case, the Staff Member, Client, and Project entities already have unique tracking numbers assigned to them, so they make great primary keys.

Just as often I’ll follow the second practice of setting the primary key to something that never occurs naturally in the database — it’s just a number or series of characters that I make up to represent the actual values on that row, called a “surrogate” key. It’s like the way your employee number at work represents your name and hire date.

An important aspect to the simple rule from above is that the primary key shouldn't change, ever. While you can change a primary key later, it's painful. This brings up an issue with the choice for the primary key. If the natural key might change or may not exist, use a surrogate or artificial key. I’ll have to do that for the Hours and Skills entities, since the values I’m storing there are not unique, and may change over time.

Apply second normal form rules to the logical ERD

Second normal form says that I need to separate out any shared attributes into separate tables. I’ve largely accomplished that goal already, but an additional part of this form is that in separating these attributes into other tables, I need to set up the foreign keys. These are the non-unique values in one table that point to the parent or relating table.

Create foreign keys

In my diagram, I already have pointer attributes (which convert to foreign keys) in the Hours entity. Notice the Project Code and Staff Code attributes in the logical diagram. In the physical model I’ve renamed those attributes to fields called Project_Code and Staff_Code.

In addition, I need to create a few more foreign key fields. I’ve added Staff_Code to the Skills table, and Client_Code to the Projects table.

It's no accident that I’ve named the foreign keys the same as the primary keys in their parent tables. This is usually a good practice, but if it isn't possible I could preface the name with FK_ or some other naming convention. Many tools will “pick up” on the duplicate names and infer that you want them to relate to each other, and some are even intelligent enough to use the Primary/Foreign Key designations to help your users design reports, screens and so on. The easier you make the process on your users, the less they need you to be involved and the fewer errors you’ll face.

Apply third normal form rules to the logical ERD

Third normal form dictates that I have to make sure that all the fields in a table depend on their primary key. It's easier to see this with an example. Let's say that I had a table called Employees with the following fields:

Employee_Code
Name
Address
Phone
Nationality

At first glance, this table might seem to conform to third normal form. But what about that Nationality field? While it is true that the employee can only have one nationality, it may violate third normal form because the nationality of an employee isn't dependent on their employee code. Nationality may need to be moved out to its own table and a relating table created to match up Nationality to Employee.

I examine my current design, and believe that I am in third normal form.

Enforce business rules with constraints and defaults

Next I need to apply some constraints to the diagram. In the tutorial regarding database objects I explained a few of the constraints you have available and how to apply them, but here's that short list again:

Keys, primary and foreign
Not Null
Check
Unique

This process is often the part that takes the longest, and requires the most care. Even in my simple database, this process requires a lot of work, so I'm going to table this part of this part of the tutorial for next week. I wanted to make sure I covered the entire process, but I want to balance that with giving this section its due.

Add any platform components

Here's where I set the fields to the data types, nullability, and other SQL Server-specific constructs. Since this part of the process is also quite lengthy, I'll cover it in the next part of the series with the constraints section.

There's more to do, and I haven't even started my indexes, storage strategy, and maintenance. Even after that, I still have to explain programming considerations such as views, stored procedures and the security. We’ll get to all that in the next few articles in this series.

< Back Page 120 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address