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

Execute SSIS Package using the Stored Procedure in T-SQL.

  • 16 February 2012
  • Author: Anil
  • Number of views: 50878
  • 0 Comments

Hello to all,

Well once again I am interested to write a new blog post and thinking on which topic I should write on then I suddenly came up with my mind regarding this Topic.

Also, this may be simply for one but for someone it will be helpful for those who don't know how to do it.

while working ,I build a SSIS package by using BIDS and we can easily execute it from BIDS project but all I want to do it from the the SQL query from SSMS coz I dont want to open the BIDS and execute the package manually while i am working in SSMS.So, after some research I found it can be done by using a store procedure called xp_cmdshell.

Generally, talking about this store procedure xp_cmdshell: "xp_cmdshell" is an extended stored procedure provided by Microsoft and stored in the master database. This procedure allows you to issue operating system commands directly to the Windows command shell via T-SQL code. If needed, the output of these commands will be returned to the calling routine.

so,to enable this we can simply run the script as:

USE master
GO
EXEC sp_configure 'show advanced options', 1
GO
RECONFIGURE WITH OVERRIDE
GO
EXEC sp_configure 'xp_cmdshell', 1
GO
RECONFIGURE WITH OVERRIDE
GO
EXEC sp_configure 'show advanced options', 0
GO

Alternatively, we can do it by using the “SQL Server 2005 Surface Area configuration” SQL Server 2005 onwards i think so.

Then ,You can run dtexec from the xp_cmdshell prompt.

The following example shows how to run a package called Package.dtsx and ignore the return code:


EXEC xp_cmdshell 'dtexec /f "C:\Package.dtsx"'

where the dtexec command prompt utility is used to configure and execute SQL Server Integration Services packages.

Also,if we need a return code from SSIS package to SSMS then,

The following example shows how to run the same package and capture the return code:

DECLARE @returncode int
EXEC @returncode = xp_cmdshell 'dtexec /f "C:\Package.dtsx"'

For this there might be a lot of solution but i simply like this method to execute the SSIS Package from SSMS by using store Procedure .

So,hope this might help someone. :)

Thanks,

Anil Maharjan

Print
Categories: Analysis Services
Tags:
Rate this article:
No rating

AnilAnil

Other posts by Anil

Please login or register to post comments.