Which is the best way??? (1 Viewer)

Anakardian

Registered User.
Local time
Today, 04:07
Joined
Mar 14, 2010
Messages
173
After getting everything to work in the first place I am now looking at improving the speed of my queries since it takes 5 to 10 seconds to make the final result.

As it is today, I have 16 queries that collect and make calculations from a variety of tables for different subjects such as budget and inspections.
Most of the queries are summed up by a single query before it is put into a temporary table.

I am wondering if it would improve the speed if I put the result of each query directly into the temporary table instead of having a query collect it all and then placing it into the temporary table?
 

mdlueck

Sr. Application Developer
Local time
Yesterday, 22:07
Joined
Jun 23, 2011
Messages
2,631
For Access, better speed resulting from the least shifting of records possible. That is, most restrictive query first, then subsequent queries with the small result set from the first query. Access DB's grow with use, so performing the most restrictive query first results in less DB bloat.

I suggest this method to prepare the DB file:
NT Command Script and Documented Steps to Decompile / Compact / Compile an Access DB
http://www.access-programmers.co.uk/forums/showthread.php?t=219948

If you have possibility to upscale to a SQL back-end, DO SO! I have had excellent success with Access being the FE to a SQL BE and all access to the BE DB is via Stored Procedures. The least data possible is actually downloaded to the FE DB which reduces FE DB bloat.

Client/Server Architecture
http://www.access-programmers.co.uk/forums/showpost.php?p=1110794&postcount=5

Example Stored Procedure / Naming Standard
http://www.access-programmers.co.uk/forums/showthread.php?t=237387
 

Anakardian

Registered User.
Local time
Today, 04:07
Joined
Mar 14, 2010
Messages
173
Thank you for your replies.
It will take some time to get through everything but by first glance I think I have much of it in already.

Moving it to a SQL server is currently not an option but maybe sometime in the future if the evolution of the database becomes more important.
 

mdlueck

Sr. Application Developer
Local time
Yesterday, 22:07
Joined
Jun 23, 2011
Messages
2,631
Just to clarify...

Moving it to a SQL server is currently not an option

I know of at least one person on this forum making use of Access FE / MySQL BE. You may host MySQL on a free Ubuntu Linux box.

In case $$$ was an obstacle.
 

Anakardian

Registered User.
Local time
Today, 04:07
Joined
Mar 14, 2010
Messages
173
It mostly has to do with the limits put in by the IT guys.
While I can make this in access, the rest is off-limits unless they have the full package including manufacturer etc. with hotline and all the bells and whistles.
 

Lightwave

Ad astra
Local time
Today, 03:07
Joined
Sep 27, 2004
Messages
1,521
I had similar restrictions managed to talk them round to a database in the test instance...............

It's a good long term plan because if like me you are given access rights to that environment you can work out all the problems and eventually they gave gave me a database in the production instance albeit I ask them to do the administration.
 
Last edited:

Users who are viewing this thread

Top Bottom