Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can identify a performance problem by doing one or more of the following:

Anchor
Examiningjobperformance
Examiningjobperformance
Examining job performance

Examining job runs over time can help you identify problematic time periods and view the general trend of the job runs. Examining how the job ran, comparing its number of executions and total duration, and analyzing a breakdown of its performance in the SQL Server can help you detect bottlenecks and discover their causes. Bottlenecks can be caused by a variety of causes, such as changes in scheduling, running the job at an inappropriate time, and offending SQLs.

...

  1. In the Time Frame list, choose the period of time you want to analyze.
  2. In the Instance list, choose the item you want to analyze.
  3. On the Association controls, in the Association area, click Jobs.
  4. On the Details tab, drill down to the job you want to analyze.
  5. On the View controls in the Main area, click Overview.
  6. In the Main area, observe how the job ran and compare the number of times it ran with the amount of time it ran.
    Compare this information to the information displayed the In MS-SQL overtime graph to see a breakdown of its performance in the SQL Server.
  7. Locate the run with the highest duration and drill down to it to view additional information.

Anchor
Examininghowjobchangesaffectperformance
Examininghowjobchangesaffectperformance
Examining how job changes affect performance

Changing a job's details may affect the performance of your system. Some changes are implemented to improve the performance of your application. Precise for SQL Server allows you track job changes and correlate them to the resource consumption of the job. This allows you to detect changes that increase the resource consumption of the job.

...

  1. In the Time Frame list, choose the period of time you want to analyze.
  2. In the Instance list, choose the item you want to analyze.
  3. On the Association controls, in the Association area, click Jobs.
  4. In the Association area, locate the jobs that have changed (indicated by a Change icon). Drill down to one of these jobs.
  5. On the View controls in the Main area, click Job Changes.
    Observe which changes were made to the job or to its steps and schedules. Determine if the job change has affected performance. For example, if you notice that a job's schedule was changed do the following:
    • On the View controls in the Main area, click Overview.
    • Check the In MS-SQL graph to see how the selected job behaved in the SQL Server over the specified time period.

Anchor
Examiningthelastexecutionofajob
Examiningthelastexecutionofajob
Examining the last execution of a job

Examining a job's last run can help you detect job failure and abnormal duration. Drilling down to the specified job run can help you learn more about its run by viewing the steps chain and the status and duration of each step.

...

  1. In the Time Frame list, choose the period of time you want to analyze.
  2. In the Instance list, choose the item you want to analyze.
  3. On the Association controls, in the Association area, click Jobs.
  4. On the Last Run tab, drill down to the job you want to analyze.
  5. On the View controls in the Main area, click Overview.
  6. View the steps chain and the status and duration of each step

Anchor
Monitoringtheoccurrencesofalerts
Monitoringtheoccurrencesofalerts
Monitoring the occurrences of alerts

Monitoring alerts can help identify when an alert last occurred, what notifications were defined on the alert, when the notifications where last sent and which operators were involved.

...

  1. In the Time Frame list, choose the period of time you want to analyze.
  2. In the Instance list, choose the item you want to analyze.
  3. On the Association controls, in the Association area, click Alerts.
  4. On the Details tab view when the alert last occurred.
  5. Drill down to an alert to observe the actions performed when the alert was triggered and whether those actions were responsible for bottlenecks.

Anchor
MonitoringadatabaseDBmaintenanceplan
MonitoringadatabaseDBmaintenanceplan
Monitoring a database (DB) maintenance plan

Monitoring a database (DB) maintenance plan can help you learn about the actions being performed in each maintenance plan and detect performance problems resulting from these actions. Drill down to a DB Maintenance Plan entity and choose the Performance view to analyze a plan's duration over time and detect problematic periods.

...

  1. In the Time Frame list, choose the period of time you want to analyze.
  2. In the Instance list, choose the item you want to analyze.
  3. On the Association controls, in the Association area, click DB Maintenance Plan.
  4. Drill down to a DB Maintenance Plan entity.
  5. On the View controls in the Main area, click Performance. Analyze how long the plan ran, during the selected time period, and try to detect any problematic periods.
  6. On the View controls in the Main area, click History. Observe the actions performed in the specified plan.
  7. Check the jobs listed in the Association area to observe how each job contributed to the entire plan and drill down to a specific job to focus on a performance problem.

...