By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,397 Members | 1,425 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,397 IT Pros & Developers. It's quick & easy.

table distribution

P: n/a
Hi all,

I have an application that use a lot of tables.

All those tables are located in 4 different mdb files.

I am wondering would it be better to put all the table in the same files?
What are the pros and the cons?

One of the table contains large binary object. I intend to leave that one in
a
separated mdb files. is that ok or it make no difference?

regards,

pierre

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Pierre" <pf@arobas.net> schreef in bericht news:ij********************@wagner.videotron.net.. .
Hi all,

I have an application that use a lot of tables.

All those tables are located in 4 different mdb files.

I am wondering would it be better to put all the table in the same files?
What are the pros and the cons?

One of the table contains large binary object. I intend to leave that one in
a
separated mdb files. is that ok or it make no difference?



Pierre,
Q1: How many is *a lot* of tables ? 20 , 40, 100 ?
Q2: What size is your backend ?

Well it depends on the application I guess, but IMO the tables should be located in *only one* backend if possible.
Maintenance and distribution is, of course, much easier when there is only one backend involved.

WHY are your tables located in 4 mdb's now ?
If you don't have a specific reason, then put them in one mdb.

If you hit Access limits you HAVE to go another way, but I see hardly any advantage when you use more than one backend.
I can in fact only think of possible corruption. (if so, not all your date is involved...).

I develop fairly 'big' databases sometimes (>500.000 records in some tables). Sometimes there are more of these big one's.
Only once I have used two seperate backends, where the second backend was merely a lookup of Postal codes.
When you use relations (RI) between the tables the table must live in the same backend.
Since I always use RI ...

--
Hope this helps
Arno R
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.