ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
High Usage of TEMP DB usage while running the Load DWH Job on MS SQL 2016
Article ID: 127869
Updated On:
Products
Clarity PPM SaaS
Clarity PPM On Premise
Issue/Introduction
After upgrading the reporting database from MS SQL 2012 to MS SQL 2016 SP2, the Load Data Warehouse job now fails due to it running out of temp space.
Steps to Reproduce:
1. Set MS SQL 2016 compatibility to 130
2. Run the Data Warehouse (DWH) job
Expected Results: There is no noticeable increase with the tempdb, and the job runs in the same amount of time as the it does on MS SQL 2012.
Actual Results: There is a considerable increase in there tempdb. The job runs longer than it did on the MS SQL 2016 or may fail if it runs out of temp space.
Steps to Reproduce:
1. Set MS SQL 2016 compatibility to 130
2. Run the Data Warehouse (DWH) job
Expected Results: There is no noticeable increase with the tempdb, and the job runs in the same amount of time as the it does on MS SQL 2012.
Actual Results: There is a considerable increase in there tempdb. The job runs longer than it did on the MS SQL 2016 or may fail if it runs out of temp space.
Cause
Caused by DE47998
Environment
Release: CODFSS99000-15.4.1-PPM SAAS FedRAMP-Sandbox-Small Environment
Component:
Component:
Resolution
DE47998 is being reviewed by engineering for a resolution.
Workaround: Set DWH schema to 120 as compatibility when running on MS SQL 2016
Workaround: Set DWH schema to 120 as compatibility when running on MS SQL 2016
Feedback
Yes
No
Powered by
