Business Intelligence Blogs

View blogs by industry experts on topics such as SSAS, SSIS, SSRS, Power BI, Performance Tuning, Azure, Big Data and much more! You can also sign up to post your own business intelligence blog.

«September 2015»
MonTueWedThuFriSatSun
31123

Executing DBCC for SQL Server Analysis Services 2016

In the upcoming release of SQL Server Analysis Services 2016, one of the new features you’ll see is the ability to perform a database consistency check against your SSAS cubes and Tabular models. Just like in the database engine side of things, DBCC for SSAS checks for corruption across the entire database or individual objects within the database.

The DBCC command is shaped likes the XMLA Process command so there’s not a lot of complexity to it. Below here, you can see the basic syntax for the SSAS DBCC command. Its worthing noting that the syntax of the command will look the same whether you’re running it against an SSAS multidimensional database or Tabular model.

"http://schemas.microsoft.com/analysisservices/2003/engine">
    <Object>
        
        
        
        
    Object>

To run the DBCC command, just open a new MDX query window and use the code seen above. Enter in the IDs of your Database, cube, measure and/or partition.

When you’re running the DBCC command against a Tabular model, there are a couple things I’d like to point out.

In the element for the CubeID, you’ll need to specify the ID of the Model. And in the element for the MeasureGroupID, specify the ID for the table you want to check.

DBCC XMLA command for SSAS

If you want to check the whole database or model for consistency, simply remove the elements the lower elements. For example, if I wanted to check the whole model, I just would leave out the elements for MeasureGroupID and PartitionID.

To find the MeasureGroupID (Table ID) or PartitionID in a Tabular model, just navigate to the Properties for that object.

Find the SSAS Tabular MeasureGroup ID or Table ID

To find the Partition ID in a Tabular model, right click the table and select Partitions. Then highlight the partition you want to check and click the Settings icon.

Find the SSAS Tabular partition ID

If you run SQL Server Profiler against SSAS while executing the DBCC command, you can see the individual checking of the columns, tables, database and more.

SSAS Tabular Profiler trace DBCC

I also ran a trace against my SSAS 2016 OLAP instance to watch each segment of

Read more
456
78910111213
14151617181920
21222324252627
2829301234
567891011

Dealing with Power Pivot to Tabular Upgrade Errors

  • 4 November 2013
  • Author: DevinKnight
  • Number of views: 7583
  • 0 Comments

Upgrading from Power Pivot workbooks to SSAS Tabular models is usually a pretty seamless process.  This is part of the beauty of the relationship between Tabular and Power Pivot.  This allows an Analyst to get started on a project using Power Pivot and when new requirements like row level security are needed IT can upgrade the workbook to Tabular and add the security feature. 

While this generally is a smooth process I often see the same couple error messages pop up for folks that are doing this.  So here’s a couple of the most common problems and how to deal with them. 

Error:  The file chosen does not contain PowerPivot content embedded in it. Choose a valid PowerPivot for Excel file.

image

Translation:  The version of Excel that you are trying to upgrade is not compatible with the version of SQL Server you are running.  This often happens when you are trying to upgrade an Excel 2013 workbook to SQL Server 2012.  You can narrow this down to the problem because if you attempt to upgrade and Excel 2010 workbook it works without any issue.

Solution:  This problem has been solved with SQL Server 2012 SP1 and Cumulative Update 4.  Install these and you shouldn’t see the issue any more.

=================================================================

Error: The PowerPivot workbook could not be imported. The service account for the workspace database server does not have permission to read from the PowerPivot workbook.

image

Translation: The Service Account that is running the SSAS Tabular does not have rights to the folder that the Power Pivot workbook is stored in.  You can find out which account this is by launching the SQL Server Configuration Manager and find the instance name.

Solution:  Grant the Service Account the permissions it needs or move the Power Pivot workbook to a folder that the Service Account does have access to.

If you know the Service Account does indeed have access but still is not able to import with this error then again you likely need to upgrade to SQL Server 2012 SP1.

Summary

As you can see both of these problems can be solved by upgrading to the latest Service Pack.  Remember SSAS Tabular was a new product to SQL Server 2012 and as you may expect with a new product if will go through some growing pains.

Print
Tags:
Rate this article:
No rating
DevinKnight

DevinKnightDevinKnight

Other posts by DevinKnight

Please login or register to post comments.