About Splitting Database.

[spenz]

I'm almost done with my very first database I've made. There is no plan for any multi-user environment or networking whatsoever.

The database will be used on just a single PC with different users depending on who's available just to encode loan transactions by the end of the day.

Having said my plan and situation, my question is, do i still need to split the database? If yes, why so? Can i get an improved speed when splitting a database? Added security like protection against corruption?

I'd like to know the advantages and disadvantages when splitting a database as it applies to my current situation. Thank you very much.

 

[SOS]

1. If you split it then you can work on a copy of the frontend without people having to be out of it.

2. It will still provide some protection from corrupting the data as the frontend will likely corrupt before the backend (not in all situations, but most).

 

[spenz]

1. If you split it then you can work on a copy of the frontend without people having to be out of it.

2. It will still provide some protection from corrupting the data as the frontend will likely corrupt before the backend (not in all situations, but most).

Thank for replying SOS. So basing from what you've said; and most specially the corruption part, I guess I'm better off with splitting my database.

But wouldn't a splitted database suffer in speed while gathering the data back and forth in the long run when we already have accumulated hundreds of thousands of records by then compared to an unsplitted database? I'm just curious..

 

[SOS]

If your database is designed properly, a split database will not have any performance differences. Check here for how to increase your database performance.

 

[spenz]

Great link man! Thanks I appreciate your advice. Will check the link now.. ^_^