From mark@cool-tools.co.uk Tue, 25 Sep 2001 10:26:27 -0700 From: "Mark Leith" Date: Tue, 25 Sep 2001 10:26:27 -0700 Subject: RE: Installing 8.1.7 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Title: RE: Installing 8.1.7 So essentially this takes us back to the old 505 extents per segment rule when dealing with a db_block_size of 8192..   Cheers for the info..   Regards   Mark -----Original Message-----From: Jacques Kilchoer [mailto:Jacques.Kilchoer@quest.com]Sent: Tuesday, September 25, 2001 16:42To: 'ORACLE-L@fatcity.com'Cc: 'mark@cool-tools.co.uk'Subject: RE: Installing 8.1.7 > -----Original Message----- > From: Mark Leith [mailto:mark@cool-tools.co.uk] > > I got a theory question.. Just because I'm not going to be > putting it in to > practice myself really :0) > > When using all of the below (LMT & UNIFORM EXTENTS, with the default > recommended extent sizes): > > How do you determine the max size a table should be for a > particular extent > size? Do any of you adopt a method of saying: > > Right, once a table reaches 500 extents, then it should be > moved to a larger > extent TS? Steve Adams has written an interesting article on the subject: Planning Extents http://www.ixora.com.au/tips/creation/extents.htm <<...For this reason, we recommend that the number of extents per segment in locally managed tablespaces be limited to the number of rows that can be accommodated in the extent map within the segment header block - that is, approximately (db_block_size / 16) - 7.>> I personally move a table when it approaches 1000 extents, out of habit more than anything else.