By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,851 Members | 1,746 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,851 IT Pros & Developers. It's quick & easy.

db2advis - Disk Limit Constraint

P: n/a
I am wondering, is the disk limit constraint in db2advis on

a) The space of the recommended indexes and materialized views.

b) The space of the recommended indexes and materialized views, as well
as the space of current indexes and materialized views.

The documentation says the disk-limit "Specifies the number of
megabytes available for all indexes in the existing schema. Specify -1
to use the maximum possible size. The default value is 20% of the total
database size."

I am not sure what that really means, I have a 206 MB index in my
database, I did run the db2advis with a 30 MB disk space constraint, it
did recommend 18 extra indexes. So I guess we are at (a) ?

Any help would be appreciated.

Thanks.

Salem

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
The design advisor does (a). It shows existing indexes and recommends
dropping some of them, but the existing indexes and dropping some of
them are not part of the disk limit. Same goes for MQTs. It should be
noted that since the input workload is possibly a subset of the full
workload, the drop recommendations only apply to the workload subset,
so may still be useful when a full workload is considered.

Nov 12 '05 #2

P: n/a
Thank you for your response. I appreciate it.

As far as I know, the user can specify if the whole workload would be
taken into consideration, or just a subset, depending on the
compression level offered (OFF, MED, LOW, HIGH).
Ivan Popivanov wrote:
The design advisor does (a). It shows existing indexes and recommends
dropping some of them, but the existing indexes and dropping some of
them are not part of the disk limit. Same goes for MQTs. It should be
noted that since the input workload is possibly a subset of the full
workload, the drop recommendations only apply to the workload subset,
so may still be useful when a full workload is considered.


Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.