It depends. A single disk drive can only handle so many I/O's per second.
You want to keep from saturating a drive's i/o s (probably saturates at
around 60 i/o's / second). So how many i/o's per second are the queries
that are coming in going to each table? Probably not an easy question to
answer. You need to distribute the i/o's accross the drives.
Jim
Tony Johnston wrote in message <36ceca16.64109149_at_news.mindspring.com>...
> I'm in the beginning stages of converting a payroll system to Borland
>C++ Builder 4 with an Orale database. The payroll system right now
>has 66 different data files. How would I get the best performance
>settiing up the database. What I mean would it be beneficial to
>create one database with 66 tables in it or split it out. The total
>size of all current files can range from anywhere between 11 megs to
>50 megs in size. The application is being designed as a multi-tier
>intranet application. Will one database file containing all these
>tables create to much drag on the system and inhibate performance?
>I would appreciate any opinions on this.
>
>Thanks,
> Tony
Received on Mon Feb 22 1999 - 07:31:32 CST
