Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
INCREASESIZE for AUTOMATIC STORAGE tablespaces
23 views
Skip to first unread message
Satish Mullapudi
Apr 24, 2013, 4:34:08 AM4/24/13
to
Hi Team,
My env details
DB2 v9.5 , AIX 5x
As given in infocenter :
"If you do not specify the INCREASESIZE clause when you enable the auto-resize feature, the database manager determines an appropriate value to use, which might change over the life of the table space."
How to determine the INCREASESIZE that the dbm is going to increase for a tablespace, when the need comes !
Thanks in Advance,
Satish Mullapudi
My env details
DB2 v9.5 , AIX 5x
As given in infocenter :
"If you do not specify the INCREASESIZE clause when you enable the auto-resize feature, the database manager determines an appropriate value to use, which might change over the life of the table space."
How to determine the INCREASESIZE that the dbm is going to increase for a tablespace, when the need comes !
Thanks in Advance,
Satish Mullapudi
Helmut Tessarek
Apr 24, 2013, 12:48:29 PM4/24/13
to
Hi Satish,
On 24.04.13 4:34 , Satish Mullapudi wrote:
> How to determine the INCREASESIZE that the dbm is going to increase for a
> tablespace, when the need comes !
This depends on your workload. How much data is inserted on a daily, weekly,
monthly basis?
The reason for the INCREASESIZE parameter is that the engine does not have to
allocate new pages for every single insert. Why? Because allocating new pages
is IO and IO can be a performance issue.
The other reason is space consumption and planning.
Therefore you use this parameter to delay/schedule this task.
--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab
On 24.04.13 4:34 , Satish Mullapudi wrote:
> How to determine the INCREASESIZE that the dbm is going to increase for a
> tablespace, when the need comes !
monthly basis?
The reason for the INCREASESIZE parameter is that the engine does not have to
allocate new pages for every single insert. Why? Because allocating new pages
is IO and IO can be a performance issue.
The other reason is space consumption and planning.
Therefore you use this parameter to delay/schedule this task.
--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab
0 new messages