Performance Testing

[LilMorePlease]

I've redesigned a database, properly normalizing it from 1 table to 8 tables.
I've imported the old data to the new database and have this project pretty
well wrapped up. I am proud of the fact that the size of the DB went down
from 95 MB to only 10 MB! What other performance measures are there to
uncover the benefits of the new database? I'm assuming I could do some query
testing to see how much faster the queries are, how do I go about timing
them?

Thanks for your help!
AA

 

[Douglas J. Steele]

Use a watch or stopwatch?

I'm not trying to be facetious. Start timing when you click on the query,
and stop when the query has returned its data.

For finer control, take a look at my April, 2004 "Access Answers" column in
Pinnacle Publication's "Smart Access". You can download the column (and
sample database) for free at
http://www.accessmvp.com/DJSteele/SmartAccess.html

 

[Tony Toews]

I'm not trying to be facetious. Start timing when you click on the query,
and stop when the query has returned its data.

But note that Access/Jet caches data. A query run a second time
without any changes can take significantly less time than the first
time.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm