External Article

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

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.

SQLServerCentral Editorial

Odd Questions

Interviews can be strange for many reasons, often because interviewers are not well prepared to evaluate candidates. This Friday Steve Jones asks you what weird things you might have encountered in an interview when someone is asking you questions.

Blogs

Creating a Striped Backup Set with AI

By

I needed to test a striped backup, so I decided to ask the AI’s...

Trace Flag 1448 – Lessons from a Technical Interview

By

In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...

Disable the sa login in SQL Server (and sleep better)

By

Disable the sa login in SQL Server (and sleep better)If you run SQL Server...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

Automatically generate tabular model partitions

By richard.powell 56882

Hi. I hope someone can give some useful suggestions. My workplace have a suite...

SQLPS and syspolicy_purge_history job

By schleep

The SQLPS.exe file has gone AWOL on 2 of my 4 SQL servers, ie,...

Visit the forum

Question of the Day

Locking Hierarchies

You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level:

SELECTo_orderdate,
        o_orderkey,
        o_custkey,
        o_storekey
FROMdbo.orders
WHEREo_orderkey = 3877;

What locking hierarchy will Microsoft SQL Server use?

 

See possible answers