Business Intelligence Architect, Analysis Services Maestro, and author Bill Pearson introduces the DAX ALLEXCEPT() function, discussing its syntax, uses and operation. He then provides hands-on exposure to ALLEXCEPT(), focusing largely upon its most popular use in removing filters from all columns in a table - except the filters we specify.
2024-01-16 (first published: 2020-10-14)
4,838 reads
Business Intelligence Architect, Analysis Services Maestro, and author Bill Pearson introduces the DAX ALLSELECTED() function, discussing its syntax, uses and operation. He then provides hands-on exposure to ALLSELECTED(), focusing largely upon its most popular use in supporting “visual totals” in Power BI.
2024-01-16 (first published: 2020-09-02)
3,647 reads
Business Intelligence Architect, Analysis Services Maestro, eight-year Microsoft Data Platform MVP and author Bill Pearson introduces the DAX CALCULATE() function, discussing its syntax, basic uses and operation. He then provides hands-on exposure to CALCULATE(), focusing largely upon its most basic uses in evaluating an expression in a context that is modified by specified filters.
2024-01-16 (first published: 2020-08-12)
7,801 reads
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
I have tried a number of times to export and then import my SSMS...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers