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

Chapter 28. CREATING MAINTENANCE ROUTINE... > REPLICATING TABLES FROM BACK END TO ...

REPLICATING TABLES FROM BACK END TO FRONT END FOR BETTER PERFORMANCE

Some tables are updated only once or twice a week, if that often. These semi-static tables could be brought into the local database and increase performance because local tables generally are faster to access than linked tables. Such semi-static tables aren't quite static enough to keep them only in the front end. The solution to this is to replicate them from the back end to the front end when the back-end version is updated.

Tip

This works great for Access-based back ends, but performance will probably be better if you leave all the tables in the back end when it's a SQL Server back end. This is because when you have queries with the data located in more than one location, Access brings all the data down locally to process.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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