Hi all,
I understand if you have your back end located on a server and use things like mysql etc you are able to analyse a query from execution through to how it returns records to be able to see any bottlenecks and also improve the efficiency of your query design.
I am wondering if there is the same funtionality anywhere when creating queries within an access database with a back end that just comes out of your split database, not upsized to a dedicated server.
I am also wondering at the same time how do developers of access applications really analyse their programs to understand where they can make performance enhancements. I do a lot of reading around performance in general but these are more to do with specific tips you find such as loading subforms only when needed, turning off certain features that can slow down your database etc. However other than visually seeing a difference I can not really benchmark anything.
I think all of these questions stem from the fact I though I had messed up the design of my database in a recent update where the program was just SO SO slow to do anything. I have loaded it up since and it runs perfectly fine which would tell me this was to do with my actual computer and nott he design of my db. At the same time, for peace of mind I would like to understand any methods used to actually test your database set up (other than the performance analyser which just keeps saying "use fewer controls").
Sorry for the lengthy post.
Regards,
Chris
I understand if you have your back end located on a server and use things like mysql etc you are able to analyse a query from execution through to how it returns records to be able to see any bottlenecks and also improve the efficiency of your query design.
I am wondering if there is the same funtionality anywhere when creating queries within an access database with a back end that just comes out of your split database, not upsized to a dedicated server.
I am also wondering at the same time how do developers of access applications really analyse their programs to understand where they can make performance enhancements. I do a lot of reading around performance in general but these are more to do with specific tips you find such as loading subforms only when needed, turning off certain features that can slow down your database etc. However other than visually seeing a difference I can not really benchmark anything.
I think all of these questions stem from the fact I though I had messed up the design of my database in a recent update where the program was just SO SO slow to do anything. I have loaded it up since and it runs perfectly fine which would tell me this was to do with my actual computer and nott he design of my db. At the same time, for peace of mind I would like to understand any methods used to actually test your database set up (other than the performance analyser which just keeps saying "use fewer controls").
Sorry for the lengthy post.
Regards,
Chris
Comment