Q
Quintus Snapper
I upsized relatively small Access DB application to SQL to be able to
access the DB from multiple locations.
The upsizing was first done locally (using the upsizing wizard in
access) and after having to do some modifications to make some of the
things that no longer worked in the forms work it all seemed to run
perfectly. That was however until we moved the SQL DB over to where we
have the SQL server hosted. After doing that, although everything
still worked it has become unbearably slow.
Since the speed was not an issue on the office LAN locally, I'm
presuming it's so slow because of the data that is being transferred.
We have a downstream internet connection 256kbs and the SQL server is
housed in a managed datacenter. Is my preumption correct and if so is
there some way of overcoming this problem? How? If not, what could the
problem be and is there a way of overcoming this problem to make it
workable again.
Thanks in advance for any help, suggestions.
Quintus
access the DB from multiple locations.
The upsizing was first done locally (using the upsizing wizard in
access) and after having to do some modifications to make some of the
things that no longer worked in the forms work it all seemed to run
perfectly. That was however until we moved the SQL DB over to where we
have the SQL server hosted. After doing that, although everything
still worked it has become unbearably slow.
Since the speed was not an issue on the office LAN locally, I'm
presuming it's so slow because of the data that is being transferred.
We have a downstream internet connection 256kbs and the SQL server is
housed in a managed datacenter. Is my preumption correct and if so is
there some way of overcoming this problem? How? If not, what could the
problem be and is there a way of overcoming this problem to make it
workable again.
Thanks in advance for any help, suggestions.
Quintus