With the size of your table you might want to consider changing it into a
fake partitioned table (assuming there is a key that it would make sense to
partition on) for better performance. While 7.3 doesn't support real
partitioning, you can create seperate tables (each in their own tablespace)
an
What about max # of datafiles?
If you're added them every 2 weeks what about making them larger? After
all, not many systems are restricted by the 2Gb file size limit any more.
Michael Hand
Polaroid Corp
-Original Message-
Sent: Monday, May 13, 2002 3:38 PM
To: Multiple recipients of
Deepender - Wracking my brain to recall 7.3. Is partitioning a feature? One
thing you might consider is to keep each of the indexes in its own
tablespace. This will give you more flexibility. I would also keep track of
the size each week to help you forecast growth. Size restrictions will
depend s
By the time you have to worry, you will have retired from the job ;-)
[EMAIL PROTECTED] wrote:
> Hi All,
>
> I have a table in my database ( size 70GB ) with size of 7GB and it has 13
>
> indexes on it. 5 Indexes are of the size 2 GB and rest are around
>
> 500-800Mb.
>
> Total size of the tab
Hi All,
I have a table in my database ( size 70GB ) with size of 7GB and it has 13
indexes on it. 5 Indexes are of the size 2 GB and rest are around
500-800Mb.
Total size of the table and indexes in total is 21GB.
The table size is increasing everyday and every 10-12 days I have to add a
da
