Multiuse DB's (2000 (9.0.6926 SP-3))

[Niven]

Hi there!

I am looking for some guidance as to designing multiuser DB

[HansV]

With a slow network, increasing the size of the database (a logical consequence of merging the four databases into one) might cause problems. If you decide to go through with it, I would certainly opt for a split design, with a shared backend and a local copy of the frontend for each individual user.

- It allows you to store temporary tables in the frontend, diminishing the probability of conflicts and of corruption of the backend.
- It allows you to provide different functionality in the frontends if needed.
- It allows you to test new or modified functionality in your own copy of the frontend without kicking out all other users.

Apart from that, make sure that you have a good backup policy. Make a full backup of the database every night as a minimum, and if possible make snapshots every few hours.

[Niven]

Hans!

Many thanks for that, it's confirmation of what I had in mind. I'm actually trying to resist those who are above me here, but basically who don't have a clue, who are saying just do it! This will enable me to resist effectively their demands. Further, this will also help me in improving the network infrastructutre here. Just to let you know, we timed the output from one DB i.e. from running the queries which extract, process, build and export the required data to the format required for Lloyd's over our network and on average it took 23 minutes (This was just one Syndicate out of 12 for all four Clients.). Locally (C: Drive), it took 30 seconds!!!!

Cheers again,

Niven <img src=/S/cheers.gif border=0 alt=cheers width=30 height=16>

P.s. Good to see you all back again.

[HansV]

Wow! Those times should convince the powers that be!