SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 272 of 365 Next >

This is the fourth article in a series of a formal process you can follow to migrate data stored in “departmental data stores” (such as Excel, text files, XML documents and so on) into a Relational Database Management System (RDBMS) like SQL Server. The first article in this series is here, and you can click the “Next” link at the bottom of each subsequent article to bring you here.

In the first installment, I explained what these data stores are, what they mean to your organization, and when they should be considered for migration. Some data doesn’t need to be stored in an RDBMS, and other data does. I also explained a few methods you can use to locate that data. That’s the first step.

In the second installment I explained how to take that data and model it so that you can tease out the requirements from the discovery you’ve done and how to model that data so that everyone agrees on its final format. I wasn’t able to complete the entire part of that process there, so I finished that step in the article that followed.

In the third installment I covered a Business Requirements document in more depth and I explained how to normalize the model into tables and columns. And in last week's installment I cleaned up the model and explained how I decided to pick the location for the data.

Here’s the outline of the process and where we are so far:

Locate the data
Model the system
Decide on the Destination
Design the ETL and Migrate the Data
Attach the front-ends
Test and Monitor

In this article I’ll explain how to select the design for the Extract, Transform and Load (ETL) process and the considerations for migrating the data. I’ll spend quite a bit of time on the process, so this warrants its own discussion. I’ll follow that in the next article by detailing the options for actually running the ETL process.

Designing the Extract, Transform and Load

The first part of an ETL process is to select the sources and destination for the data. In my case, there’s only a single source, and it happens to be a Microsoft Excel Spreadsheet, version 2007. That’s really important, because no matter what tool I use I’ll need to know the way that the source deals with the data. Every method will handle the source in a very specific way, so it’s important to get that information.

In fact, I didn’t even ask the businessperson to tell me the version of Excel they were using. I went to their desk, opened the spreadsheet and clicked on “Help” and then “About” to verify the exact version they were using. Then I copied the spreadsheet to start my experimentation with the different methods, and right-clicked that file to verify the version. You should document carefully this part of the process — it really does matter.

Of equal importance is the destination. I’m using SQL Server 2008 Enterprise Edition for this exercise, and that will make a difference in the data types, field structures and so on. The point is that you should understand both the source and destination carefully before you start.

You may have more than one source. If so, document those the same way.

Mapping Fields

The next step is to map out the fields you want to bring in. In my case, the spreadsheet is quite de-normalized. That means that several elements of data are “missed” in with each other — there are Vendor names in the same “record” (line) as the Client name in the spreadsheet and so on.

What I’ll do is map out each element I need in the tables, and work backwards to the source. Remember that I built the database from the Business Requirements, so the database is now the “gold standard” of the data I need. I can do this electronically, or just on paper, but in any case I basically draw a line from the cell in the spreadsheet to the table and column in the database. It should end up as a one-to-one mapping — with the relationships defined in a subsequent step.

This means in some cases I’ll have to break apart some cells in the spreadsheet into multiple discrete values. If you’ll refer back to the example spreadsheet I posted in an earlier article, you’ll see that City, State and Zip Code are actually all in one cell. Depending on how I extract the data and which tool I use, this might actually be done graphically for me, but if not, I draw a line from the single cell to a box showing the transformation, then on to the database tables and columns they belong to. For instance:

Figure 1

I do this for each “task” or step in the ETL process. In some cases this is so simple that paper and pencil will suffice, in other cases, the tool you pick will create this graphic for you. In any case, no matter how “simple” the transformation may appear, you need to follow this process.

Determining Differences

A spreadsheet is arranged much differently than a database. In fact, one database (such as Oracle) there are differences. This step involves analyzing those differences from every angle — from something generic such as normalized versus de-normalized data to the actual data types and the structure. I’ll start with the generic task of making the relationships work.

As I normalize the data, I’ll have to keep the keys or relating values from the “parent” table stored somewhere as I break out the “child” data into its respective tables. For instance, I have in my diagram the Vendor separated from the Vendor Type, since a Vendor might supply my company with more than one service or good. But in the spreadsheet, the users have placed commas between the “types” values, so I have to transform them just as I did a moment ago with the addresses. But while the address goes into the same table, the Vendor Types gets its own table — and I’ll need to tie those back out. So I’ll make a mark on the map when I need to do that indicating the pairing key or value. In my case it’s the Vendor Code.

The relationship part of ETL is possibly the hardest. It requires that you thoroughly understand the source data and the destination design. This is when those Business Requirements really help.

The next part of analyzing the differences is checking the data types. Excel is especially vulnerable in this area, since it does have strong data types that the user can choose, and Excel chooses its own (Unicode text in most cases) if the user doesn’t. This is where the Entity Relationship Diagram comes in handy — I’ve taken the time to show the data types on my diagram, and working through the spreadsheet to understand two things: What types for the columns the user chose and what types the system chose when the user did not. Once again, this goes on my paper or electronic data map.

Finally there is the “optionality” of the data. This simply means where the data is required, versus where it is actually available in the source. For instance, based on the Business Requirements, I want to enforce that any time there is a contact, that contact must be tied back to a Vendor. In some cases, that might not be true in the source data. So what should you do?

There are a couple of choices. One is to ask the business to enter that data in the source system. This will be the richest, most correct data you can get, but in some cases it’s just not possible. Either there isn’t time, the business doesn’t want to do that or some other reason.

In that case, you can leave that record out, or place it in another table to deal with later. This protects the purity of your data the best, but might not be acceptable to the business.

The third option is to generate the data. This can be dangerous, but if you are careful it can work. I normally opt for this approach (depending on the situation of course) and enter some static value like “Not Yet Available” or “TO DO: Enter contact name” or some value that maintains the integrity of the system, but enters the parent record anyway.

You’ll have to figure out what makes sense for your situation.

In the next installment I’ll explain how to choose and create the ETL process and implement the extraction and load.

InformIT Articles and Sample Chapters

My article series on database design starts here.

Books and eBooks

Database Design for Mere Mortals is a great book on database design.

Online Resources

You can learn more about Business Process Model Notation here.

< Back Page 272 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