Time Slicing Group By slow performance on a large MSSQL dataset (DE60359)

book

Article ID: 212088

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

DE60359 Time Slicing Group By slow performance on a large MSSQL dataset

STEPS TO REPRODUCE:

  1. On a large MSSQL dataset connect to Clarity
  2. Run Time Slicing Group By manually

Expected Results: The job to complete in a timely manner

Actual Results: The job is processing very slow (up to 400 min), the culprit is the query below:

select min(id) as minpk, max(id) as maxpk, count(id) as totalRows from ( select TOP( 1 ) id from fin_cost_plan_details where id > 5000000 and (odf_nk_billing_cost is null and BILLING_COST is not null ) order by id ) alias1

Workaround: None

Environment

Release : 15.9.1

Component : CA PPM TIME SLICING

Resolution

This is DE60359, in review by Engineering

Important:

Note the usage of the job: The Time Slicing Group By has to be run once initially after upgrade to 15.9.1, and then running it every 5 min is not necessary. It can only be ran as/if needed. The data will be updated by the regular Time Slicing job.