Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Sizes - a nice easy request
Wed, Jan 21 2009 8:07 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

I'm trying to work out the consequences of some table structure changes in terms of file sizes. Is there a guide anywhere? I had a look through the help pdf and couldn't spot anything.

If it included suggestions on calculating index sizes that would be a major bonus.

Roy Lambert

Wed, Jan 21 2009 10:51 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< I'm trying to work out the consequences of some table structure changes
in terms of file sizes. Is there a guide anywhere? I had a look through the
help pdf and couldn't spot anything.

If it included suggestions on calculating index sizes that would be a major
bonus. >>

There really isn't any way to calculate index sizes ahead of time without
knowing the actual data, due to the compression used.  For non-primary key
indexes, the size of the index will be smaller (compared to a full index
without compression) as the amount of duplicate index keys in the index
grows.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Jan 21 2009 1:00 PMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Tim


In that case hows about the data? I seem to remember a post about you'd reduced the size of storeage needed for an integer.

Roy Lambert
Wed, Jan 21 2009 6:16 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< In that case hows about the data? I seem to remember a post about you'd
reduced the size of storeage needed for an integer. >>

Not integers, but the size of DECIMAL/NUMERIC columns is much smaller (-28
bytes), and the size of BLOB column information in a row is smaller by 4
bytes.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image