Path: news.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!cyclone2.usenetserver.com!news.webusenet.com!news-hub.cableinet.net!blueyonder!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail From: "Jonathan Lewis" Newsgroups: comp.databases.oracle.server Subject: Re: Oracle 8i Database with 18,000 Partitions Date: Mon, 11 Nov 2002 18:07:04 -0000 Lines: 72 Message-ID: References: <7a7ecd29.0211110955.456e6112@posting.google.com> NNTP-Posting-Host: jlcomp.demon.co.uk X-Trace: news.demon.co.uk 1037038074 15328 158.152.75.41 (11 Nov 2002 18:07:54 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Mon, 11 Nov 2002 18:07:54 +0000 (UTC) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Newsreader: Microsoft Outlook Express 4.72.3110.5 Xref: newsfeed1.easynews.com comp.databases.oracle.server:166565 X-Received-Date: Mon, 11 Nov 2002 11:07:40 MST (news.easynews.com) If the idea is to have a table of around 600,000,000 rows, split by customer into about 15,000 partitions, then at first sight, this looks like an accident waiting to happen. Key issues how are you going to define it - range or hash ? are you planning to index it - that's another 15,000 partitions per index to worry about. are all queries guaranteed to be structured to do maximum partition elimination ? If not, then 15,000 searches to find a small amount of data will produce a massive processing overhead. One important point - can you clarify what you mean by 'restored'. -- Regards Jonathan Lewis http://www.jlcomp.demon.co.uk Next Seminar dates: (see http://www.jlcomp.demon.co.uk/seminar.html ) ____England______November 12/14 ____USA__________November 19/21 (Dallas) The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html Tom Glover wrote in message <7a7ecd29.0211110955.456e6112@posting.google.com>... >First of all, I am not an Oracle DBA. Secondly, this DB design is not >my idea - so bashing the messager is not required (I'm just the poor >sap that has to make the application around the database work!). > >I have a third party vendor who is pushing a customer database design >that will contain over 15,000 partitions. Basically, each customer >will have a partition with approximately 30,000 - 50,000 records. The >partitions can be restored on a very regular basis (100 - 200 >customers per day possible). So, I have a few questions as to the >feasibility of this design: >1. What are the performance impacts of this many partitions? I have >read numerous discussions about as many as 4,000 partitions and the >general consensus was: you can do it, but you better be very,very good >and careful. >2. Is Oracle even designed to handle this volume of restores (100-200 >per day)? What are the pitfalls (maintainance???) to supporting this >many restores. >3. If the answers to the questions above lead to the point that this >system can be made to work, what level of DBA do I need to 1)Create >the database and stored procedures and 2) Maintain this monster of a >system once it is turned over. > >Any help is greatly appreciated.