Thank You for your explanation, really appreciate it.
During Batch window SLG Tier has 85% global weight with all 4 workloads in SLG Tier 1 and no other levels present, there are no Tactical workloads defined in the system so everything goes to SLG and below. We suspect that whenever Large volume of Reporting queires classified under Timeshare runs on the system along with Batch jobs, the job gets delayed. Queries running in Timeshare are short reporting queries and some of them takes 1-2min to complete though some of them are skew.
Can concurrency or skewness in low priority Timeshare impact upper higher priority workloads, we verified that High priority workloads are not waiting for AWT for long period.
Thank You for your explanation, really appreciate it.
During Batch window SLG Tier has 85% global weight with all 4 workloads in SLG Tier 1 and no other levels present, there are no Tactical workloads defined in the system so everything goes to SLG and below. We suspect that whenever Large volume of Reporting queires classified under Timeshare runs on the system along with Batch jobs, the job gets delayed. Queries running in Timeshare are short reporting queries and some of them takes 1-2min to complete though some of them are skew.
Can concurrency or skewness in low priority Timeshare impact upper higher priority workloads, we verified that High priority workloads are not waiting for AWT for long period.