This document discusses converting SQL queries from Microsoft Access to SQL Server for improved performance when queries are slow in Access or when moving to a .NET application front-end. It outlines reasons for translation like gaining speed by executing queries in seconds instead of minutes and enabling the move to .NET. The document also previews a demo database that will be used to illustrate lifting tables from Access to SQL Server and re-linking queries.
Ensure the security of your HCL environment by applying the Zero Trust princi...
Translation
1. Converting SQL from Access
to SQL Server
Andrew Couch
ASC Associates
www.upsizing.co.uk
2. Topics
• Reasons for translating SQL
• How to translate SQL
• Basics of translation
• Deeper problems with translation
• Further issues
• Final points
www.upsizing.co.uk
3. Reasons for translating SQL
• Performance
– Your queries, reports, forms, excel spreadsheets are
slow to open.
– Complex sequences of query operations are slow, for
example when importing and batch processing large
amounts of data.
– Typical gains, a query taking 2 minutes improves to
execute in 2 seconds.
• Moving to .NET
– You are planning on moving from an Access front-end
to a .net application.
www.upsizing.co.uk
