Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Sven Schuran asked how to set extent size and next size for a fragmented table. Keith Simmons said to use EXTENT SIZE and NEXT SIZE as for a plain table. Gerd Kaluzinski warned the sizes apply to every fragment and cannot differ per fragment. Sunil Thakkar advised a modest first extent and a next size for growth, noting round robin differs.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Schuran, Sven — — source: IIUG Forums & Mailing Lists
Hi,
When I try to fragment a table, how to specify the extent size and next
extent size.
Thanks Sven
↪ replying to Schuran, Sven
Keith Simmons — — source: IIUG Forums & Mailing Lists
Sven
The same way you do with a plain table: EXTENT SIZE .... NEXT SIZE ....
Keith
On 25/10/06, Schuran, Sven <sschuran@maske.de> wrote:
>
> Hi,
>
> When I try to fragment a table, how to specify the extent size and next
> extent size.
>
> Thanks Sven
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Hi,
given extent size and next size is allocated in all fragements, so be careful
that your tables do not grow by factor of fragmentation !
There ist no way to define the extent size different for some fragments.
Regards,
gerd
>
> Hi,
>
> When I try to fragment a table, how to specify the extent size and next
> extent size.
>
> Thanks Sven
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
_______________________________________________________________________
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222
Sevn,
As mentioned by others - use Extent size and next size. However, since
this table is fragmented - I would use a reasonable smaller extent
(minimum extent required for all the fragments) as the first extent -
and the growth factor for the next extent.
This way you will be sure that all the fragments has a good initial
extent and only those fragments that require more space will grow based
on the next extent.
It also depends on the fragmentation strategy - for round robin the
above does not hold true - or if you really understand your data and
spread them equally then the above will be less effective but it will
still hold true.
Thanks,
Sunil Thakkar
Sr. Consultant - DBA
|| Office: 720.493.7012 || Cell: 720.299.6464 || Fax: 720.920.4000 ||
sunil.thakkar@bearingpoint.com || www.bearingpoint.com
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Schuran, Sven
Sent: Wednesday, October 25, 2006 3:36 AM
To: ids@iiug.org
Subject: Fragment by expression and extent size [7670]
Hi,
When I try to fragment a table, how to specify the extent size and next
extent size.
Thanks Sven
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
********************************************************************************
*******************
The information in this email is confidential and may be legally privileged
Access to this email by anyone other than the intended addressee is
unauthorized. If you are not the intended recipient of this message, any
review, disclosure, copying, distribution, retention, or any action taken or
omitted to be taken in reliance on it is prohibited and may be unlawful. If
you are not the intended recipient, please reply to or forward a copy of this
message to the sender and delete the message, any attachments, and any copies
thereof from your system.
********************************************************************************
*******************
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.