Performance Analyzer

T

Té

Hi. I'm new to Access. I'm not sure if I understand exactly what the
performance analyzer does. I think it makes recommendations on your
database, but how exactly does it do that?

Can someone please simplify this in new Access dummy user terms please! lol
 
A

Albert D. Kallal

Té said:
Hi. I'm new to Access. I'm not sure if I understand exactly what the
performance analyzer does. I think it makes recommendations on your
database, but how exactly does it do that?

It makes recommendations by simply telling you not to do certain things that
are known over the years to cause some issues of performance.

For example if you're driving a car, I could recommend you that it's a
really bad idea to start the car moving by using second or third gear, This
is going to be hard on the clutch. So, I would recommend to you that it's a
good idea to start the car moving by using 1st gear.

In many cases a lot of the recommendations the performance analyzer comes up
with are really very poor, and really won't help your application that much
in terms of speeding up the application.
 
A

Albert D. Kallal

Té said:
Hi. I'm new to Access. I'm not sure if I understand exactly what the
performance analyzer does. I think it makes recommendations on your
database, but how exactly does it do that?

It makes recommendations by simply telling you not to do certain things that
are known over the years to cause some issues of performance.

For example if you're driving a car, I could recommend you that it's a
really bad idea to start the car moving by using second or third gear, This
is going to be hard on the clutch. So, I would recommend to you that it's a
good idea to start the car moving by using 1st gear.

In many cases a lot of the recommendations the performance analyzer comes up
with are really very poor, and really won't help your application that much
in terms of speeding up the application.
 
D

David W. Fenton

I think I'm right in saying that
by default Access automatically creates a unique index on a column
whose name ends with ID.

By default, yes, but I think most professional developers turn this
option off.
 
D

David W. Fenton

I think I'm right in saying that
by default Access automatically creates a unique index on a column
whose name ends with ID.

By default, yes, but I think most professional developers turn this
option off.
 
D

David W. Fenton

More advanced programming techniques will sometimes drop indexes
and then recreate them after updating data to enhance update
performance

I would say that's useful only the case of mass updates/inserts of
100s of thousands of records. This is not a common scenario, and I
can't imagine a production app using a Jet back end in which it
would have any use at all. If operations of that magnitude are part
of the daily use of the application, you'll very soon outgrow a Jet
back end, I'd say.
 
D

David W. Fenton

More advanced programming techniques will sometimes drop indexes
and then recreate them after updating data to enhance update
performance

I would say that's useful only the case of mass updates/inserts of
100s of thousands of records. This is not a common scenario, and I
can't imagine a production app using a Jet back end in which it
would have any use at all. If operations of that magnitude are part
of the daily use of the application, you'll very soon outgrow a Jet
back end, I'd say.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top