• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 29. Upsizing a Desktop Applicati... > Correcting the Upsize Result

Correcting the Upsize Result

Unless you’re upsizing an extremely simple application (but then if you are, why are you upsizing?), you’ll have some work to do after the Upsizing Wizard finishes. You’ll also need to consider many of the corrections listed in this section if you’re upsizing your desktop database by hand.

Adding Relationships and Constraints and Fixing Indexes

You might have had to remove some relationships so that the wizard will run. The wizard might also have reported that it could not define some of the relationships that it found in your desktop database. The same is true for validation rules. Also, the wizard does not define your primary key indexes in the most optimal way, and it often creates multiple indexes on the same column in the upsized table. The multiple indexes occur because Access actually defines additional hidden indexes when you define referential integrity between two tables. In a desktop database, these additional indexes are actually aliases of the original index, so they don’t take up any additional resources. In a database upsized to SQL Server, these additional indexes use additional resources and are unnecessary.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint