Re: Creating multiple tables within a tablespace

Jeff:

I don't know what the limits are for OpenVMS, but sooner or later, you will run into the maximum datafiles limit for that OS. Most installations use tablespaces in one of two ways:

1. General level grouping: you might have (in addition to SYSTEM, RBS, TEMP) DATA1, DATA2, INDEX1, INDEX2, TOOLS. or
2. App-specific grouping: you might have (in addition to SYSTEM, RBS, TEMP) APP1_DATA, APP1_INDEX, APP2_DATA, APP2_INDEX, etc.

Good luck,
Dave

Jeff Hunter wrote in message <34ECC4D5.2EA2B2AC_at_isrv.com>...
>Greetings,
>
>We have a database with over 150 tables. Some tables
>may have 2,000,000 rows with record lengths of
>around 400 bytes. We currently are creating
>one tablespace per table in an Oracle 7.1 database
>running on OpenVMS. We are questioning the advantages
>and disadvantages of logically grouping several tables
>into larger tablepspaces thus reducing the total number
>of tablespaces we have to maintain. What are the compelling
>advantages of having multiple tables per tablespace when
>most of our tables are of this magnitude.
>
>Kindest Regards,
>Jeff Hunter
>
>--
>
>Jeffrey Hunter Internet: jhunter_at_isrv.com
>Programmer/Analyst WWW: www.isrv.com/~jhunter
>PO BOX 832 Voice: (412) 284-7325
>Butler, PA 16003-0832 FAX: (412) 789-9601
>
>
Received on Sat Feb 21 1998 - 00:00:00 CST