Re: Query Speed ... Access XP vs Access 2000
From: Alex Ivanov (consul_at_collegeclub.com)
Date: 03/05/04
- Next message: Frank M.: "How to convert a value when importing"
- Previous message: Douglas J. Steele: "Re: "Auto numbering""
- In reply to: David Sumlin: "Re: Query Speed ... Access XP vs Access 2000"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Mar 2004 08:57:20 -0800
With adp all SQL processing is done on the server. You will eliminate huge
overhead of downloading all the data from all tables mentioned in a query
that match selection criteria (and often even that don't match the criteria
at all) and assembling the recordset on the client. Some folks may object on
this statement, saying that Jet engine performs some optimizations to the
queries before it sends the requests to the SQL server, but the key word
here is "some", which is better translated to "almost no".
On the other side conversion of a complex access database to an adp project
is not an easy process and sometimes partial conversion may be preferred.
You convert Access queues into SQL Server Views and stored procedures and
link your Access tables to the views and/or use pass-through queries to
access the data.
Alex.
"David Sumlin" <anonymous@discussions.microsoft.com> wrote in message
news:4DC7AD87-2388-4BB9-8B39-295404A6D9A6@microsoft.com...
> Yes, I've made sure everybody had latest Windows & Office Service Packs &
Patches installed.
>
> I didn't try converting it to a .adp. What do you think that would show
me?
>
> Also....do you think there might be some sort of behind the scenes
selection of jet vs ado retrieval going on that would make that kind of
difference?
- Next message: Frank M.: "How to convert a value when importing"
- Previous message: Douglas J. Steele: "Re: "Auto numbering""
- In reply to: David Sumlin: "Re: Query Speed ... Access XP vs Access 2000"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
