Validating sql syntax
This white paper presents techniques for improving performance and updatability in Office Access applications that use tables linked to SQL Server.
(22 printed pages) Click here for the Word version of this article.
Introduction Understanding and Addressing Performance Issues Understanding and Addressing Updatability Issues Addressing Application Logic and Coding Issues Creating Unbound Office Access Applications Conclusion Microsoft Office Access supports three primary options for connecting to data stored in Microsoft SQL Server databases: This paper focuses on the challenges encountered by Office Access developers who rely on the Office Access (Jet) database engine to connect to SQL Server over ODBC.
The most common way this is done is by creating linked tables in Office Access that use the SQL Server ODBC driver to connect to tables in SQL Server databases.
The SQL Server Migration Assistant (SSMA) for Office Access enables you to convert an Office Access database to this type of application by moving your Office Access data to new SQL Server tables and linking to these tables.
Any forms, reports, queries, or code that previously worked with the original Office Access tables are automatically connected to the new SQL Server tables.
In an application that uses linked SQL Server tables, two different database engines are at work: the Office Access/Jet database engine that runs on the Office Access client and the SQL Server database engine.
The interaction of these two engines can sometimes yield results that are inferior to those obtained by using only the Jet database engine with native Office Access tables.
This is the type of application created by using the SQL Server Migration Assistant for Office Access.Instead, it submits multiple queries, often including queries that request all of the rows in a table, and then it combines or filters the data on the client.If the criteria require local processing, even queries that should return only selected rows from a single table can require that all the rows in the table be returned.There are two tools that you can use to see how Office Access is communicating with SQL Server.
To listen in on the conversation from the server side, you can open the SQL Server Profiler and create a new trace.The primary strategy for improving performance is to minimize the amount of data returned to the Office Access client and maximize the amount of processing that occurs on the server.