1. It depends what dbms you're using. If you're using an enterprise system like SQL Server, then you'd be talking billions. If you're using something like Access on the other hand... who really knows with that. Better to estimate on the smaller end of the scale though. I have one SQL Server db with 200 tables that I manage, and it works like a charm.
2. I can't really envisage a need for splitting a db simply because of the db size. Split it if it is containing completely separate applications, but not if all the objects are part of the one app. So long as you normalise your db, and index where necessary, then it should keep working ok with a million tables - so long as your hardware is configured properly.
Just my opinion though...
Marcus.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
