Beginning ASP.NET 2.0 and Databases (Wrox Beginning Guides) - page 17

Chapter 1 - Displaying Data on the Web

byJohn Kauffman, Fabio Claudio Ferracchiatiet al. ?
Wrox Press ?2002

Summary

In this chapter, we have discussed the advantages and disadvantages of creating data-driven sites, showing that although they can provide a wealth of functionality, there are problems associated with their creation. This was followed by an introduction to data sources, and how they are handled using ADO.NET. The architecture of an application that involves data access was then covered, showing why the separation of data and presentation can provide many benefits to developers. Finally, details about MSDE - the database server we'll use in examples throughout this book - were given, and the product was installed.

Now that the background to the creation of data-driven web sites in .NET has been dealt with, we can move on to finding out the details of each of the technologies, and putting them to use. In the 7 covering the adding, modification, and deletion of records. The rest of the book then makes use of this knowledge of ADO.NET, discussing the creation of components , applications, and stored procedures, and looking at performance issues. We finish with a case study, which pulls all this knowledge together in a practical application.

Chapter 2 - Relational Databases

byJohn Kauffman, Fabio Claudio Ferracchiatiet al. ?
Wrox Press ?2002

Chapter 2: Relational Databases

If you're already familiar with database theory, you may just want to skim this chapter. But if you're new to databases, or you feel that you need a bit of a refresher, this chapter is intended to provide you with enough theory to prepare you for those that follow. In it, we'll become familiar with the key concepts and common terms that you will run across throughout your career as a database developer and user . Relax, become familiar with the ideas, and don't get caught up on any one issue if it doesn't make sense to you right away. You can always refer back to this chapter later as a reference.

We'll begin with a discussion of a few key database concepts, such as tables, rows, and fields. Then, we'll explore the key differences between relational and non-relational databases. After that, we'll provide an introduction to SQL, to database design, and to normalization. We'll conclude with a brief comparison between SQL Server and Microsoft Access. By the end, you'll know enough to smooth your passage through the next few chapters, and you'll have a base upon which the rest of the book will build.

Database Terms and Concepts

The term 'database' has many interpretations, the simplest of which is 'a collection of persistent data'. By this definition, a hard drive is a database, since it is certainly a repository of data. But to software developers, a database is much more than ad hoc data on a hard drive. The definition we will use here is more specific, and more useful to software developers who use database management systems (DBMSs) for application development.

Note

A database is a collection of persistent data that is stored in tables.

A table is a collection of rows.

A row is a collection of fields.

A field is a repository for a value.

Even this definition is not particularly narrow - these criteria are met, for example, by properly formatted comma-separated value files ( .csv files), and by spreadsheets. Consider this example of the former:


Herbert Hoover, Ex-President


Marcus Welbey, M.D.


Gandalf, The Grey


Jabba, The Hutt


Attila, The Hun

This whole file represents a single table in a database that contains information about people. Each row in this file represents a row in the table, and contains information about one person. Each row contains two fields: the first is the person's name , and the second is the person's title. And finally, the fields have values - for example, the first field of the first row has the value Herbert Hoover .

However, although 'databases' such as this one have their place (and we looked this subject in the previous chapter), this book will concentrate for the most part on the kinds of database that are managed by DBMSs, of which well-known products such as SQL Server and Microsoft Access are but two examples. Such systems are responsible for managing the details of storing and retrieving physical data in the form of a database, and making that data available to the developer.

In this chapter, as in the rest of the book, we'll be basing our experiments on and around the sample Northwind database that not only comes with the MSDE we've already installed, but also is available for MS Access and MS SQL Server version 7.0 and later. Northwind is a fictitious company that buys products from suppliers and sells and ships them to its customers. The Northwind database, like our .csv example above, contains tables, one of which is named Customers . This table, like all of the others in the Northwind database, contains rows and fields.

Try It Out - Our First Look at Northwind

{% if main.adsdop %}{% include 'adsenceinline.tpl' %}{% endif %}

In this chapter, we're going to use Microsoft Access as our tool for analyzing the Northwind database. If you don't have Access installed, that's not a problem - we'll be illustrating the discussion with screenshots that show exactly what's going on. The Access version of the Northwind database ships with the product, or you can download it from the Microsoft web site (http://office.microsoft.com).

Assuming that you have Microsoft Access on your computer, locate the Northwind.mdb file in the Program Files\Microsoft Office\Office\Samples folder, and double-click on it to open it in with Access. If you get a dialog asking you to convert the database, accept the option - you'll need it later on.
Choose the Tools Relationships... menu item to display the relationship diagram for the Northwind database:
This diagram includes all of the tables in the Northwind database, but for now, let's take a closer look at the Customers table that we can see in the above screenshot:

From the diagram above, you can see the fields in each of the tables - but didn't we just say that a table is a collection of rows, not a collection of fields? The thing is, when we're designing a table in a database, or just looking at the tables in a relationship diagram, we are only interested in the fields that make up each row that the table contains. Every table in the Northwind database has rows, every row contains the fields that appear in the relationship diagram, and every field in each row has a value (see below).
Later in this chapter, we'll discuss how to view and modify the data (that is, the rows and values) in a table. For now, you can just return to the main Database window, ensure that Tables is selected in the Objects list, and then double-click on the Customers table to see the rows of data it contains: