![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Do you make "Flush Package Cache Dynamic" part of your RUNSTATS routine ? In other words do you follow runstats with FLUSH PACKAGE CACHE DYNAMIC at the end ? I was reading Websphere best practices when it comes to db maintenance scripts and saw the flush package statement at the end and wondering if it is necessary. As a matter of fact, if you created a new index for a table with existing data, are you suppose to runstats for that index too ? Look forward to your replies. Thanks. RL |
#3
| |||
| |||
|
|
Do you make "Flush Package Cache Dynamic" part of your RUNSTATS routine ? In other words do you follow runstats with FLUSH PACKAGE CACHE DYNAMIC at the end ? I was reading Websphere best practices when it comes to db maintenance scripts and saw the flush package statement at the end and wondering if it is necessary. As a matter of fact, if you created a new index for a table with existing data, are you suppose to runstats for that index too ? Look forward to your replies. Thanks. RL |
#4
| |||
| |||
|
|
As a matter of fact, if you created a new index for a table with existing data, are you suppose to runstats for that index too ? |
#5
| |||
| |||
|
#6
| |||
| |||
|
|
Thank you experts. *I never heard of COLLECT option on CREATE INDEX before but will use it now. Is it same as runstats for index ? RL |
![]() |
| Thread Tools | |
| Display Modes | |
| |