Reasonable number of table partitions?

[Matt McLeod]

I'm currently doing the prep for a move from ASE 12.5.4 to 15.0.3 and
am looking at table partitioning (in particular range-based
partitions) and thinking they could be awfully useful to us.

Is there some maximum number of partitions it is reasonable to use? I
have data going back up to ten years and am trying to figure out if I
should partition it based on year, month, or quarter. Typically once
data goes in it's never changed, so should I even look at just having
one big partition for everything that could be considered "archival"
and then do a new partition each month or quarter?

I've looked in the performance and tuning manuals plus the references
and there doesn't appear to be much discussion of how to best make use
of table partitions.

Thanks,

Matt

[Rob V [Sybase]]

For range partitions, you can safely have a few hundred partitions in your
table (as opposed to list partitions where this is not recommended and you'd
typically have not more than,say, 10).

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

mailto:***@sypron.nl
http://www.sypron.nl
Sypron B.V., Amersfoort, The Netherlands
Chamber of Commerce 27138666
-----------------------------------------------------------------

Post by Matt McLeod
I'm currently doing the prep for a move from ASE 12.5.4 to 15.0.3 and
am looking at table partitioning (in particular range-based
partitions) and thinking they could be awfully useful to us.
Is there some maximum number of partitions it is reasonable to use? I
have data going back up to ten years and am trying to figure out if I
should partition it based on year, month, or quarter. Typically once
data goes in it's never changed, so should I even look at just having
one big partition for everything that could be considered "archival"
and then do a new partition each month or quarter?
I've looked in the performance and tuning manuals plus the references
and there doesn't appear to be much discussion of how to best make use
of table partitions.
Thanks,
Matt