Database Reference
In-Depth Information
System Behavior Analysis Against Baseline
The default behavior of a database application changes over time because of various factors such as the following:
Data volume and distribution changes
Increased user base
Change in usage pattern of the application
Additions to or changes in the application's behavior
Installation of new service packs or software upgrades
Changes to hardware
Because of these changes, the baseline created for the database server slowly loses its significance. It may not
always be accurate to compare the current behavior of the system with an old baseline. Therefore, it is important
to keep the baseline current by creating a new baseline at regular time intervals. It is also beneficial to archive the
previous baseline logs so that they can be referred to later, if required. So while, yes, older baselines are not applicable
to day-to-day operations, they do help you in establishing patterns and long-term trends.
The counter log for the baseline or the current behavior of the system can be analyzed using the Performance
Monitor tool by following these steps:
1.
Open the counter log. Use Performance Monitor's toolbar item View Log File Data and
select the log file's name.
2.
Add all the performance counters to analyze the performance data. Note that only the
performance objects, counters, and instances selected during the counter log creation are
shown in the selection lists.
3.
Analyze the system behavior at different parts of the day by adjusting the time range
accordingly, as shown in Figure 5-7 .
 
Search WWH ::




Custom Search