Maximizing SQL Server Capabilities
WHAT'S IN THIS CHAPTER?
- Understanding the reasons to upsize a database to SQL Server
- Walking through the upsizing process
- Reviewing techniques and methods when using a SQL Server
WROX.COM CODE DOWNLOADS FOR THIS CHAPTER
The wrox.com code downloads for this chapter are found at www.wiley.com/go/proaccess2013prog.com on the Download Code tab. The code is in the Chapter 21 download and individually named according to the code filenames listed throughout this chapter.
As you read in an earlier chapter, Access works well with SQL Server. When you use SQL Server as the back-end database engine for your solution, you tap into a powerful server-based system. Using Access as the front end allows you to design a robust and feature-rich user interface. Combining the two together in your database solutions enables you to create a solid, high-performing database solution for your clients.
This section focuses on existing Access solutions that utilize Access data files rather than SQL Server. Although a few of those may have been designed with upsizing in mind, a relatively small portion of the others may need and benefit from using a SQL Server database engine as the back end (BE).
There are a variety of reasons for choosing to upsize to SQL Server. This chapter helps you evaluate your solutions to determine if they will benefit from upsizing, what the upsizing process entails, and what to look for as you are going through the process.