Large DB extents or not

B

bvanmeer

New Member
Hi all,

We are getting a bit confused, openedge consultants don't agree on this fact. What is now the best way if fi i got a database of 100Gb, i can create 5 large extents of 20GB or 50 normal ones of 2Gb?

Does anyone have the do's and don'ts on this?

Thx,

Benny
 
How many storage areas do you have in your database?
Did you optimize the storage area design (tables and indexes in distinct storage areas, for example)?

The reason I am asking is because it might have an influence on how large the files will get when you, for example, put a high-volumne OLTP table in its own storage area, that is only 10GB large.

Heavy Regards, RealHeavyDude.
 
RealHeavyDude said:
How many storage areas do you have in your database?
Did you optimize the storage area design (tables and indexes in distinct storage areas, for example)?

The reason I am asking is because it might have an influence on how large the files will get when you, for example, put a high-volumne OLTP table in its own storage area, that is only 10GB large.

Heavy Regards, RealHeavyDude.
Click to expand...

Fore some databases we did, but still very basic like Tables and index split. I saw also the discussion already going on about extents where Tom answered that if the OS supports it you can just do it, there are no real restrictions.

Greetings,

Benny
 
If you have 100GB of data you darned well better have multiple type 2 storage areas.

Using large extents is fine. These days I don't even think about making any fixed extents until I see variable extents in the 16GB range. Which is not a hard and fast size to start making them fixed -- it is just my personal threshold for starting to think about it. Today, February 22nd 2012. Tomorrow I might think 64GB is the new threshold ;)
 
You must log in or register to reply here.
Back
Top