Re:Database Sizing doubts..

From: <dgoulet_at_vicr.com>
Date: Thu, 25 Jan 2001 09:15:38 -0500
Message-Id: <10752.127473@fatcity.com>

Manivannan,

Sizing tables and indexes is VERY crucial in more ways than one. First within an application now two tables contain the same number of or size of rows. Therefore it is a waste of space to size all the tables according to the needs of the largest, which is the direction your headed. Second while a small amount of fragmentation is not necessarily bad you do pay for it when the data required spans across those extent divides, so one would want to minimize it. Lastly from a DBA's perspective, if you (as the developer) can't provide me with an idea of how big the tablespaces need to be, I can assure you they will be too small so be prepared for user complaints.

Over here, I'm pretty nice to my developers. I ask them only to provide a map of what the schema will look like (never mind the tablespaces, etc... an ERD works fine), how many rows each table will contain and the time frame in which those rows will occur. I then do the size & dispersal figuring.

Dick Goulet

____________________Reply Separator____________________

Subject: Database Sizing doubts..
Author: "Manivannan.M" <manivannan.m_at_tatainfotech.com> Date: 1/25/2001 1:51 AM

Hi list

We are in a dilemma over a database creation for an application

We have created a database (having 8 tablespaces -- application related only) .When we are actually sizing and creating the tables and indexes in these tablespaces, we are confused as to how these should be created.

We were told by some people that Oracle does not recommend creation of INITIAL and NEXT segments for the database objects and it should take the default size of the tablespace as the segments should be uniform size.

We were told by some others that specifying INITIAL and NEXT is very important for all the tables and indexes , esp for the tables growing rapidly growing in size(say at the rate of 7000 records/day with row size around 700 bytes/record).In the case of large tables like these, can we do away with INITIAL and NEXT extents and instead specify MINEXTENTS value as 40 or 50?

Waiting for your valuable inputs!!

Thanks in Advance..

                                        Manivannan Muthukrishnan.

-----------------------------------------------------------------------------
    ADDRESS:                             E-MAIL:
    68/4, Site no:3,                     manivannan.m_at_tatainfotech.com
    80 Feet road,                        
    (opp) Deccan Studio,
    Indiranagar,                         PHONE:
    Bangalore - 560038.                  5284681  Ext: 464
------------------------------------------------------------------------------

--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Manivannan.M
INET: manivannan.m_at_tatainfotech.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may Received on Thu Jan 25 2001 - 08:15:38 CST