SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 274 of 365 Next >

This is the last 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 article, 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 article I covered a Business Requirements document in more depth and I explained how to normalize the model into tables and columns. After that I cleaned up the model and explained how I decided to pick the location for the data.

In the last two tutorials I explained how to design your Extract, Transform and Load (ETL) process, and what your considerations are for data type conversions and so on. The last tutorial covered the actual implementation of that process, using multiple approaches.

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 the final part for my project, and I’ll give you other options for your own. It’s also not a-typical to see multiple processes used, based on what you need to do.

Front-End Options

There are multiple ways to access data from SQL Server, but the first thing you need to decide is whether your users need to just read the data or enter, edit and delete data. If all they need to do is to see the data, then your options are very simple. You can use everything from a simple web page using a script to Reporting Services. Both are no-cost options for the most part — just a little time invested in the process. In fact, if all you need is to show the users the data, you can actually look at it using Excel and the “External Data” option.

But things are rarely that simple. Recall that my example started many tutorials ago with the users importing some data from another system and then adding their own entries to it. For that, Microsoft Office Excel really isn’t a good fit. Yes, you could code things to work that way, but it takes a lot of work that way and turns out not to handle those multi-table inserts as well as it should.

So you’re left with a few other choices — but don’t worry. Programming database applications is one of the most documented forms of development. I’ll cover the options you have, along with the pros and cons of each form, for creating applications that read, write and update data.

Web Applications

Years ago it was fairly difficult to develop good applications for a web browser that could easily edit data in a database. This is not only no longer the case, but actually the default application space for many shops.

Whether you use PHP, ASP, ASP.NET or any of the other programming acronyms, you can find a free or low-cost method to write a web page that accesses a database. I won’t cover those code types in this article, since InformIT has books, articles, guides and tutorial that already do that.

The basic layout for a web application involves the code for the browser to interpret, the web server with either optional or built-in extensions to handle the calls to the database, and the database server itself. I’ve seen all three on the same server (for testing, normally) or more often spread out onto multiple systems.

I’ll point out some of the references we have on InformIT for this kind of programming at the end of this tutorial.

The next most popular method to allow your users is to code up a desktop or “fat” client application that you compile into an executable program. Once again there are lots of helps right here on InformIT for that, and I’ll point to those at the end.

Don’t be concerned with cost in this area, either. You can download the Express editions of Visual Studio even to write commercial programs, all for free.

If you’re after the fastest, easiest way to write code against a database, this is it. You simply write the code, compile it and hit the database. Of course, it’s more complicated than that, but the simplicity of dragging a grid to the screen and pointing it to a stored procedure or table is really hard to beat.

Middle Tier

At the more complicated end of the spectrum is writing either a web-based or desktop-based “front end” application that communicates with another process (called a “middle tier”) that in turn connects to the database. The advantages here are that the database code and business logic can be separated out from the graphical front-end, or what is called the “presentation layer.”

Once again, I’ll provide some links for middle-tier programming at the end of this article.

Database Decisions

While I haven’t covered the specifics on the front-end code for your project, I do have some definite opinions on how you should set up the database. In addition to the design work you’ve done on the database tables and keys, I always advise that you consider using stored procedures and/or functions along with views to control the access to the system.

The first advantage in a stored procedure, function or view is that it abstracts the database structure away from the application. You can ensure that the same stored procedure always works for the application even if you need to add or take away a column or table. In the case of a stored procedure or function (but not necessarily a view) you can see performance gains as opposed to sending direct Transact-SQL code from the application.

Don’t misunderstand — there’s no such thing as “always” in coding. There are exceptions to just about all “rules” that someone (including me) comes up with.

Another very important advantage to using stored procedures and functions is that they can help protect you from SQL Injection attacks. SQL Injection isn’t a SQL Server (or any database) issue; it’s a coding issue. Let’s take an example.

Say that you have a box on the screen where the user enters a part number: 1234.

Now assume that the code that runs when the user clicks looks something like this:

SELECT PartDescription
FROM InventoryTable 
WHERE PartNumber = ‘ <ENTERED VALUE FROM WEB PAGE> ‘;
GO
An enterprising user might type this in the box:
1234’; GO SELECT * FROM InventoryTable; GO ‘
Which would translate in your code to this:
SELECT PartDescription
FROM InventoryTable 
WHERE PartNumber = ‘1234’; GO SELECT * FROM InventoryTable; GO 
‘ ‘;
GO

And they would be able to see what they shouldn’t. A stored procedure, however, can test for that extra “tick” mark or even fail with special logic if more than one string is entered in. Of course, you could do that with code as well, but this protects the database even when the developer forgets to do that.

Test and Monitor

Once everything is all hooked up, make sure you create and run your tests for the users. It isn’t just ensuring that the data is correct and is handled the way you expect — you should also consider writing some code that sends a lot of data to the test server and then deletes it to check to ensure performance and design.

And now is the perfect time to take a performance tuning baseline, since no one is on the system. This will form a good platform to check against periodically. You can read more about how to do that here.

By the way — I hooked up an application for my users when I migrated the data. You might be surprised by my choice — I used a Microsoft Access “Database Project.” That’s right — I used a department-level application to solve a department-level application problem! Here’s my logic:

My users already have Access, and are comfortable with making reports in it. I was able to code up and application in just a few minutes that made calls to the proper views, functions and stored procedures, and there’s no Access database files involved — it’s just a very rich graphical interface. There are best-practices for this, so make sure and do a web search on that topic.

InformIT Articles and Sample Chapters

Here is a great article on Web programming: ASP.NET 2.0: Is It Really This Easy?

One on general programming: The Essence of LINQ

And another on Middle-Tier programming: Middle-Tier Patterns in .NET

Books and eBooks

Here is a great book on Web programming: AJAX, Rich Internet Applications, and Web Development for Programmers

One on general programming: LINQ Unleashed: for C#

And another on Middle-Tier programming: .NET Patterns: Architecture, Design, and Process

Online Resources

You could even use Access to create a web page — not recommended, but interesting.

Free programming tools from Microsoft

Middle-Tier programming

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