DB extent sizes best practice?

[gracera]

What is the maximum size for a fixed DB extent?
Is there a best practice for calculating the appropriate size for your DB fixed extents?

I'm running Progress 9.1E04. We have several databases, the sizes range from 13GB to less than 100mb.

 

[TomBascom]

Maximum extent size is governed by:

1) The Progress "large files" setting -- if not set you are limited to 2GB
2) The OS may have a limit.
3) The filesystem that the extent lives on may have a limit which might be different from that of the host OS.
4) Available disk space.

There is no simple best practice size that works for everyone.

My advice:

0) Gain an understanding of how fast your data grows.
1) Think about how often you'd like to be adding extents.
2) Verify your OS and FS limits.
3) Enable large files if necessary or convienent.
4) Use extents that are big enough so that your data fits comfortably without having to add new ones more often than step #1.

Personally I use 8GB extents a lot these days. I also use a lot of much smaller extents in storage areas that are smaller -- some extents are just a few mega-bytes.