Hi everyone,
I'm having speed issues with my database. It's a small DB with about 20 users nationwide. The server is located in Toronto and users from Toronto, Montreal and Vancouver use it. The problem is that it's a big server and there's alot of network traffic which makes running queries and opening forms a very slow process.
The database is currently split so what we were thinking of doing is having a local backend in each center and have them pool their data togheter with the main back end.
That would make searches and queries a local affair and would prevent the slowdowns. At the same time the synchronization with the main backend should be seemless.
I'd like to hear your opinions on how I should proceed with this and what steps should I take.
p.s. I thought about having 1 workstation stay open and at the end of the day (at a certain time) just append the data to the main backend but we can't have 1 unattended workstation running like that...
I'm having speed issues with my database. It's a small DB with about 20 users nationwide. The server is located in Toronto and users from Toronto, Montreal and Vancouver use it. The problem is that it's a big server and there's alot of network traffic which makes running queries and opening forms a very slow process.
The database is currently split so what we were thinking of doing is having a local backend in each center and have them pool their data togheter with the main back end.
That would make searches and queries a local affair and would prevent the slowdowns. At the same time the synchronization with the main backend should be seemless.
I'd like to hear your opinions on how I should proceed with this and what steps should I take.
p.s. I thought about having 1 workstation stay open and at the end of the day (at a certain time) just append the data to the main backend but we can't have 1 unattended workstation running like that...