Analysis Services (SSAS)

External Article

Get a Descriptive Name for SQL Server Analysis Services Profiler Event Class and Event Subclass

  • Article

A customer provides an SQL Server Analysis Services trace file to analyze. You save this file into a trace table and execute T-SQL code to analyze the results. Rather than getting descriptive values for the EventClass and EventSubclass data, you get numerical values. How do you resolve these numerical values to meaningful descriptive names? Check out this tip to learn more.

2012-05-17

2,275 reads

External Article

Enabling Drillthrough in Analysis Services

  • Article

Data analysis from a cube starts with aggregated and summarized data, followed by drill-down and drill-through of the data for a deeper and intelligent analysis. Drill down is inherently supported when you browse the data of the cube, but drill through has to be defined as per the requirements of analysis. In this tip we will see how to enable drill through on a cube.

2011-10-11

2,890 reads

External Article

How to remove parent as a child from a SSAS parent child dimension

  • Article

In a parent child dimension, when an attribute's usage type is set as Parent and browsed from a client tool, many designers as well as users may get confused based on the displayed results. For example, when you browse a parent attribute in a parent child dimension like Employee and say the parent attribute is Employees, you can browse data members from the parent node until the deepest available level of the child node. By default you will find each parent member having a child member with the same name even though this member might not exist in the data. From a user experience point of view this is not a desirable way of browsing a parent child hierarchy because it may get confusing. In this tip we will look at an example of this issue and how to solve this problem.

2011-05-06

2,757 reads

External Article

Backup and Restore of an Analysis Services Database

  • Article

One of the most important responsibilities of a database administrator is to make sure that all the databases are backed up across environments managed by them. In my earlier article titled Importance of Database Backups and Recovery Plan I discussed the importance of a good database backup and recovery plan for all the user and system databases. In this article we will take a look at the steps which a database administrator needs to follow to backup and restore an analysis services database.

2011-04-25

3,172 reads

External Article

How to reduce MDX code redundancy in SQL Server Analysis Services (SSAS)

  • Article

To query an Analysis Services cube, MDX is used as the query language. In most business settings, one would find a set of queries that are common across a number of user query requirements. To cater to this, even with a modest size IT team, there is a good chance that the same queries are developed redundantly either within a SSAS MDX script or repetitively in an ad-hoc manner in client applications. In this tip we would look at how to reuse queries without redeveloping them over and over.

2011-03-01

3,774 reads

Blogs

Flyway Tips: Multiple Projects

By

One of the nice things about Flyway Desktop is that it helps you manage...

What DevOps Look Like in Microsoft Fabric

By

Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...

T-SQL Tuesday #192: What career risks have you taken?

By

I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...

Read the latest Blogs

Forums

Can an Azure App Service Managed Identity be used for SQL Login?

By jasona.work

I'm fairly certain I know the answer to this from digging into it yesterday,...

Azure Synapse database refresh

By Sreevathsa Mandli

Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...

how to write this query?

By water490

hi everyone I am not sure how to write the query that will produce...

Visit the forum

Question of the Day

Fun with JSON I

I have some data in a table:

CREATE TABLE #test_data
(
    id INT PRIMARY KEY,
    name VARCHAR(100),
    birth_date DATE
);

-- Step 2: Insert rows  
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT *
FROM OPENJSON(
     (
         SELECT t.* FROM #test_data AS t FOR JSON PATH
     )
             ) t;

See possible answers