Editorials

Access and SQL Server – Tips for Optimization

Featured Article(s)
Tips and tricks on improving SharePoint search in larger organizations
MOSS 2007 search is not just about single page result set coming from the same MOSS 2007 site; there are many hidden values in this piece of functionality available out of the box. Check out what you have been missing out on in MOSS 2007 search.

Webcast TOMORROW – Register Now
Protect & Defend Your Data

With most SharePoint implementations storing critical business data, it is crucial that this data be protected and quickly restorable in the event of a disaster. Learn how utilizing Data Protection Manager 2007 as your backup/restore/disaster recovery solution provides a full-fidelity solution with granular control. We will walk you through the initial configuration of DPM as well as setting up a recovery farm. Presented by: Christopher Regan

> Register Now
> Live date: 12/2/2009 at 12:00 Pacific

Access and SQL Server – Tips for Optimization
I know a good number of people do indeed use Access as a client to SQL Server, either for writing reports or simple forms or building applications in the Access toolset. SSWUG.ORG reader Chris wrote in with some suggestions for making the love-hate relationship between SQL Server and Access better. Here’s what he had to say:

"I used to work with the combination of MS Access using the JET engine to connect to SQL Server for several years. The cases where join queries are processed in Access usually happen when an Access function or operator is in the Access SQL. You can always modify things to get the majority of the query joins and filtering done in the SQL Server engine. In some cases you might need to replace parts of a complex Access query with sql server views. I haven’t worked much with Access for several years, but here are a few observations I recall from the older days:

1. The combination of a MS Access front end using the JET engine with linked tables and sql server can work really well.

2. The Access queries sent to sql server retrieve the primary keys of the tables in the query. Using this information you can create good covering indexes. Access will pick up the extra columns in the background using batches of parameterized queries retrieving the rows based on the primary key values it retrieved in the main query. This mechanism is only used if you are using linked tables with JET.

3. A left join in Access is updatable if the select list includes the join column values from all the tables. You have to include the redundant values in the select list.


I know that I have left out many details. With a bit of experimenting with profiler, you can deduce how the Access/SQL Server combination works. Then you can get it to work a lot better than is commonly believed.
"

Announcing: SQL Server Security Virtual Workshop
Registration is now open – The virtual workshop will be on December 10 and will be all about SQL Server Security – I’ll be going through what you want to know to understand options, what security is all about with SQL Server and where to look to lock things down. This virtual workshop will bring you up to speed on setup options, best practices, what SQL Injection is all about and a lot more. We will be issuing certificates on completion of the short quiz after the workshop and I’ll be available live for Q&A during the workshop.

[Get More Information] or [Register Today]

Featured White Paper(s)
Performance Optimization: Extending the IT Infrastructure
Due to time, money, and resource limitations it is often no longer feasible to rewrite, re-architect, or even replace under-p… (read more)

Featured Script
Flag only the duplicate Rows
Flag duplicate rows, leaving the 1st row one of each kind not flagged… (read more)