New DB Compacts to half the size?

[PeteCresswell]

I'm creating a work DB on-the-fly and then populating it.

I'm pretty sure that the code is deleting the DB and the recreating it
from scratch each time it runs.

After the process is over, the DB's size is right at 2 gigs. (Beeeeeg
process...)

But if I compact it, it shrinks down to "only" one gig.

Seems to me like if I create a DB from scratch, populate it, but don't
update it that it should be as small as it can be.

Hopefully I'm wrong.

Anybody?

[Michael \(michka\) Kaplan [MS]]

After compact is when a db is smallest from a data perspective -- mere
population does not lead to minimal size.

In other words, your observations is what should truly be expected here.

--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.

"PeteCresswell" <Go**********@FatBelly.com> wrote in message
news:74**************************@posting.google.c om...

I'm creating a work DB on-the-fly and then populating it.

I'm pretty sure that the code is deleting the DB and the recreating it
from scratch each time it runs.

After the process is over, the DB's size is right at 2 gigs. (Beeeeeg
process...)

But if I compact it, it shrinks down to "only" one gig.

Seems to me like if I create a DB from scratch, populate it, but don't
update it that it should be as small as it can be.

Hopefully I'm wrong.

Anybody?