SQL Server vs. Access
For our final act in this chapter (and
therefore just prior to
Microsoft Access can be a good database choice when you need a relatively small-footprint, relatively inexpensive database that resides on the client. However, performance begins to breaks down for large databases, and for many simultaneous users. Using Access as a server-side database for even small databases will yield poor performance, since Access does not have a server component. That is, the client application always has to read the entire table from the file server (that is, the computer on which the Access database resides), even if the SELECT is requesting a single record.
Microsoft SQL Server is much more expensive, and
may be subject to license fees per
As we described in the previous chapter, to a large extent MSDE is SQL Server, but without client tools like the Query Analyzer and the Enterprise Manager. Without the aid of these tools, routine database maintenance becomes more difficult - but not prohibitively so, as you'll soon see.
In this chapter, we've scratched the surface
Chapter 3: Connecting to a Data Source
As we discussed in Chapter 1, all of the interactions between ASP.NET and data that you'll see in this book will start with an ADO.NET connection . The connection establishes what data source the page will use, the security details necessary to authorize access to the data, and the data provider that will handle the translations between the data source and the ADO.NET objects. However, the syntax you use to create the connection, and the options available to you, vary considerably with different sources of data.
You know that in ASP.NET, getting data from a
database to the web page that your users will see in their browsers
requires a number of ADO.NET objects: connections, datasets, data
readers, data adapters, and so on. In order to provide useful