- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- How many tables in a manageable database
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2002 12:47 AM
тАО12-05-2002 12:47 AM
How many tables in a manageable database
The development teams are still throwing tables at me (DBA) and growth of table numbers is around 40% pa.
If ever I question the need for a new table I get accused of hampering progress.
Any opinions on how many tables is manageable/supportable/sensible ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2002 02:09 AM
тАО12-05-2002 02:09 AM
Re: How many tables in a manageable database
depends a bit on your machine but try to get through to your users
DBA Rules ok. Make them justify the tables.
http://www.orafaq.com/faq.htm is a very good data source and should help you make up your mind about limits.
Regards
Steve Steel
Quote of the moment
-------------------
"We are drowning in information but starved for knowledge."
-- John Naisbitt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2002 07:34 AM
тАО12-05-2002 07:34 AM
Re: How many tables in a manageable database
You may find it actually gets easier to run your system with more tables in some regards, ie. the more tables you have the more storage you require which gives you a better chance at being able to eliminate hot spots by migrating particularly heavily hit tables into low activity areas.
Reorganising the 1.5TB of data on the other hand takes a little while ;)
In answer to your question however you might find that at some point a few Oracle tools might help out, my personal choice are the Quest tools Spotlight SQLab and Space Manager, all of which are excellent for management/tuning and are relatively cheap as database tools go.
Regards,
Robert Thorneycroft
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2002 07:54 AM
тАО12-05-2002 07:54 AM
Re: How many tables in a manageable database
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2002 08:03 AM
тАО12-05-2002 08:03 AM
Re: How many tables in a manageable database
As a more or less extreme example, our Baan ERP system utilizing an Oracle database currently has over 60K tables and over 250K indices. Moreover, the table and column names are almost gibberish so that unless you have the meta-data that describe these columns and tables, it's very difficult to run queries against the database itself.
I would say that a 40% annual growth rate indicates a flaw in the design process. I suppose that I suffer a bit from radical idea that you design first and then code. In the ideal development world, there would be no new tables needed. In the real development world, a moderate number of new tables would be expected but your growth rate indicates that not nearly enough effort went into the initial design phase.