External Article

Cracking DAX – the EARLIER and RANKX Functions

So far in this series, Andy Brown of Wise Owl Training has shed light on functions like CALCULATE, VALUES and FILTER, but it’s only when you understand the idiosyncrasies of the EARLIER function that you can claim to have genuinely cracked DAX. This article gives four examples of the use of this peculiar function, in the process explaining why it has such a misleading name. Using the EARLIER function properly all boils down (as is so often the case with DAX) to understanding row and filter context. The article also shows how to use the RANKX function to sort data into your required order.

External Article

Scaling SQL Monitor with your growing estate

Tony Davis describes the features and capabilities of SQL Monitor that allow it to scale smoothly to monitor a growing estate of servers and databases, while still providing a single, simple dashboard that gives the team all of the essential SQL Server metrics and alerts, establishes baselines, and detects trends in behavior.

Blogs

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

BCA KCP Kas Tlogosari No.Tlp.083179431643

By wiseenglishedu

Jl. Tlogosari Raya II No.28, Tlogosari Kulon, Kec. Pedurungan, Kota Semarang, Jawa Tengah 50196

BCA KCP Pintu Air Telp:08213111109

By innosys

Jl. Pintu Air Raya No.36 Q, Ps. Baru, Kecamatan Sawah Besar, Kota Jakarta Pusat,...

BCA KCP Kranggan No.Tlp.083179431643

By wiseenglishedu

Jl. K.H. Wahid Hasyim No.7, Bangunharjo, Kec. Semarang Tengah, Kota Semarang, Jawa Tengah 50137

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers