db growth: unused size of reserved size

[Former Member]

Hi,

In the last 6 month we had a unethically high growth of the reserved size of our database.

In db02 "db space history" we see the following values (layout 0all_columns; all values in KB; db size = 350 GB)

<u>Date - reserved size - data size - index size - unused size</u>

01.01.2007 - 286.099.568 - 154.760.280 - 43.966.312 - 87.372.976

01.12.2006 - 280.246.848 - 154.526.592 - 43.498.072 - 82.222.184

01.11.2006 - 267.480.720 - 152.204.920 - 42.568.912 - 72.706.888

01.10.2006 - 254.344.440 - 149.296.184 - 41.770.688 - 63.277.568

01.09.2006 - 247.372.352 - 146.998.136 - 41.111.048 - 59.263.168

01.08.2006 - 239.666.632 - 144.891.192 - 40.467.744 - 54.307.696

01.07.2006 - 229.658.104 - 143.376.624 - 39.804.888 - 46.476.592

01.06.2006 - 219.132.120 - 138.857.440 - 38.411.192 - 41.863.488

The growth of the values "data size" and "index size" are (more or less) constant. But the "unused size" is growing faster and faster.

I realized that "reserved size" = data + index + unused size

My questions: What is the "unused size" and why is this value growing faster and faster? Can I reduce the "unused size"? Is this behavior typical?

Thanks in advance

Wolfgang

[Former Member]

Hi Wolfgang,

please have a look at the "Autogrowth" function of your db-files. Do they grow by a certain percentage or by a static value. If they grow by a certain percentage, could that explain the unused space?

Regards,

Sven

[Former Member]

Hi Wolfgang,

Unused size in database it is a space reserved for new data objects, eg. new documents, new generated objects etc.

When You generate object from transaction SGEN, Your transaction log may grow very fast. This is a typical behavior.

You may reduce unused space by shrinking database or database files in Enterprise Manager.

Regards,

Marcin Gajewski

please reward points for helpful answers