1199
CHAPTER
SQL Server as an
Access Companion
IN THIS CHAPTER
Linking to SQL Server tablesUnderstanding SQL Server
database objectsM
icrosoft has increasingly positioned Access as a gateway to SQL
Server data. SQL Server, of course, is Microsoft’s flagship enter-
prise database engine, and it’s frequently used to drive mission-
critical applications for tens of thousands of companies around the world.
Because of its excellent scalability, fault tolerance, transaction logging, and
other features, SQL Server is often used as the data store behind large Web
sites, for data warehousing, and for business intelligence purposes.
Depending on installation specifics, SQL Server is able to serve many thou-
sands of users simultaneously. From SQL Server’s perspective, an Access
application making requests for data is just another user — and it’s treated
no differently from any other client.
Access projects are used to create and maintain SQL Server Express data-
bases, or SQL Server Enterprise databases. You can also use an Access proj-
ect to create the user-interface objects and forms, reports, macros, and
modules that utilize data from SQL Server. The database window for a proj-
ect looks very similar to the Access database window you’re already accus-
tomed to. In fact, creating the user-interface objects is virtually the same as
creating them in Access.
On the CD-ROM
This chapter uses a database named Chapter37.accdb. If you haven’t
already copied it onto your machine from the CD, you’ll need to do so now.
The CD also includes Chapter37.mdf and Chapter37.ldf, the SQL
Server database files to attach to a SQL Server instance on your computer.
In general, SQL Server Express automatically installs on the same computer
you use for development. Even though SQL Server is a server database, by
default SQL Server Express installs as a client-side service retaining all its
database server features.