Bill Pearson


Stairway to MDX

Stairway to MDX - Level 2: The Ordinal Function

Business Intelligence Architect Bill Pearson introduces the MDX Ordinal Function, as a means for generating lists and for conditionally presenting calculations. He also demonstrates the use of the function in creating datasets to support report parameter picklists.

You rated this post out of 5. Change rating

2019-03-26 (first published: )

19,852 reads

Stairway to MDX

Stairway to MDX - Level 3: The Order() Function

The Order() function provides the 'hierarchized' sorts you need for reports and applications using MDX. In this Step, Business Intelligence Architect Bill Pearson explores using the versatile Order() function for providing dataset sorts that respect dimensional hierarchies.

You rated this post out of 5. Change rating

2019-03-26 (first published: )

12,971 reads

Stairway to MDX

Stairway to MDX - Level 5: Members, and an Introduction to the MDX Members Functions

Bill explains what is meant by a 'Member' and 'Member function' in MDX. A member is an item in a dimension that include the 'measures' which are the values of the attributes that belong to a dimension. 'Measures' are themselves members of a dimension called the “measures” dimension. MDX has a set of functions, known as member functions, each of which allow us to perform operations upon any member of a dimension

You rated this post out of 5. Change rating

2019-03-26 (first published: )

9,448 reads

Stairway to MDX

Stairway to MDX - Level 12: : MDX Time/Date Series Functions: OpeningPeriod() and ClosingPeriod() Functions

BI Architect Bill Pearson continues with the second of a set of articles surrounding a group of MDX functions specialized to support the analysis of data within the context of time / date. In this article, we will explore the OpeningPeriod() and ClosingPeriod() functions, and get hands-on practice with each in meeting sample business requirements.

You rated this post out of 5. Change rating

2015-07-22

4,838 reads

Stairway to MDX

Stairway to MDX - Level 11: MDX Time/Date Series Functions: PeriodsToDate() and Derivative Shortcut Functions

BI Architect Bill Pearson launches a set of articles surrounding a group of MDX functions specialized to meet the pervasive business need to analyze data within the context of time / date. In this article, we will overview the PeriodsToDate() function, and then we will introduce "shortcut" functions that are based upon it.

You rated this post out of 5. Change rating

2015-06-17

9,781 reads

Stairway to MDX

Stairway to MDX - Level 10: “Relative” Member Functions: .CurrentMember, .PrevMember, and .NextMember

SSAS Maestro, SQL Server MVP and Business Intelligence Architect Bill Pearson introduces three “major players” within the MDX “relative” functions. These basic, but highly employed, functions include the .CurrentMember, .PrevMember and .NextMember functions.

You rated this post out of 5. Change rating

2013-06-12

7,543 reads

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...

SQLPS and syspolicy_purge_history job

By schleep

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

Be Wary of Data

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Be Wary of Data

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