Forum Discussion
Access and Azure SQL Database
Hello Jose - thank you for your post. I'm experiencing similar issues, but with an MS Access backend on azure with a frontend linked to those tables. It's not a bandwidth issue because even a small form that is not bound to a table takes upwards of a minute to open up in design view. (Although it's not recommended, I tried everything on sharepoint and it is very fast - however, that will most likely corrupt the database as it tries to make copies of the file as different users update the db.)
At this point, I'm considering setting up a cheap server at the company to host the database backend and put the frontend on a network, locally or even on sharepoint.
Have seen similar issues about speed on azure even with MS SQL server, but I can't imagine that to be the case since there must be commercial applications running on it all the time.
Thanks,
Chris.
Did you optimize your forms to only retrieve single records rather than entire tables? Did you apply dynamic loading to listboxes, combo boxes, subforms, ...? Have you switched to using pass through queries and views wherever possible? Have you done any analysis to validate your indexing of table/fields?
Also, nothing will ever be as fast as a web system where both the backend and front-end are on the same system. Hybrid databases are pushing/pulling the data continually over the Internet, this will always be a relatively slow process. The true solution is to use proper web technologies:. PHP, .net, MySQL, Azure, ... I have migrate several Access database to such platforms and the difference is staggering. It's a question of picking the right to for the job and Access was never meant for anything WAN related.
