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

SQL Server 2012 PowerPivot for Excel Prerequisites Error

  • 5 April 2012
  • Author: BradSchacht
  • Number of views: 154
  • 0 Comments

PowerPivot was a great new tool when it released several years ago.  Now the newest version is out along side SQL Server 2012.You can still install the 2008 R2 version of PowerPivot or you can try out the new 2012 RTM version.  There are some nifty improvements that Devin Knight has chronicled (Blog | Twitter). There are several requirements that are not part of the 2008 R2 requirements.  The install instructions are the following with the first step being the new requirements:

There are plenty of blogs out there discussing the error message that says you need to install the proper version (32 bit or 64 bit) because you downloaded the incorrect one for the version of office installed. However, I installed both the prerequisites (.Net 4 and Visual Studio Tools) and still had the following error:

"Microsoft SQL Server 2012 PowerPivot for Excel Setup Setup is missing prerequisites:

This add-in requires the Microsoft Visual Studio 2012 Tools for Office Runtime and the .NET Framework 4.0. For more information, go to "

Come to find out if you have both of these already installed and then try to install PowerPivot and get this error message the fix is pretty simple and one that is not listed on the Microsoft page about the install.

You have to install the components in a certain order:

  1. .Net Framework 4.0
  2. Microsoft Visual Studio 2010 Tools of Office Runtime
  3. PowerPivot 2012 for Excel

The problem I had was installing the Visual Studio 2010 Tools, then .Net Framework 4.0 then PowerPivot. Luckily you don't need to roll everything back. Simply uninstall the Visual Studio 2010 Tools and reinstall them, this way they are put on the system AFTER .Net 4. I tried running a repair on the Visual Studio Tools about 4 times at different point after the .Net 4.0 install was finished with no luck. I did a simple uninstall and immediate reinstall and everything worked PERFECT!

So when setting up PowerPivot 2012 be sure to install in the order listed above.  If you do switch number 1 and 2 just uninstall the Visual Studio Tools and run the install again. Worked like a charm.  

Print
Categories: Blogs
Rate this article:
No rating
BradSchacht

BradSchachtBradSchacht

Other posts by BradSchacht

Please login or register to post comments.