SSAS 2016 Question about whether if there is a partition level failure level (ETL) for whatever reason will it take down the cube in its entirety?

Paul Mauriello
Paul Mauriello used Ask the Experts™
on
We are using SSAS 2016 Enterprise

We are building a mega cube with multiple companies data and we want to partition by Company.
We also will want to schedule separate ETL schedules for each company.


Question is in the event there is failure from a partition perspective will that take down the entire cube? In the event the data from one company goes wonky?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Raja Jegan RSQL Server DBA & Architect, EE Solution Guide
Awarded 2009
Distinguished Expert 2018

Commented:
>> Question is in the event there is failure from a partition perspective will that take down the entire cube?

It really depends upon the type of error you receive on your partition or cube level and the type of Error configuration you have configured at the Cube/partition or dimension level.
More info about Error configuration below..
https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/error-configuration-for-cube-partition-and-dimension-processing?view=sql-analysis-services-2017

>> In the event the data from one company goes wonky?

Yes, if ignore the error at partition level, then the data available for that error ed partition company might not be correct. It can be abnormal..
Paul MaurielloSoftware Programmer Developer Analyst Engineer

Author

Commented:
I researched.

As long as the processing command is wrapped in a transaction, the cube will remain in a good/query’able state should data from one company go wonky and cause a processing job to fail.

 
https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/processing-options-and-settings-analysis-services?view=sql-analysis-services-2017
https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/batch-processing-analysis-services?view=sql-analysis-services-2017

in terms of Proactive caching does this still hold true?
SQL Server DBA & Architect, EE Solution Guide
Awarded 2009
Distinguished Expert 2018
Commented:
>> in terms of Proactive caching does this still hold true?

Yes, it holds true here as well.
Proactive caching suggests when to update the cube when the source data changes and SQL Server will internally handle those in a transaction.
So, it should be fine..
Paul MaurielloSoftware Programmer Developer Analyst Engineer

Author

Commented:
Thank you :)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial