Thinking about your DAX Queries like a SQL Query in Power BI 

Amazing! Do a whole playlist on DAX Queries. I think it is the most effective way to learn DAX / think in DAX! Thank you and keep em coming!

Brilliant. What would be even better is if we could use an actual SQL query directly thus be able to leverage all that SQL expertise.

Thank you Patrick, explaining how to handle that pesky "Query(1,1) The expression specified in the query is not a valid table expression" message. This was driving me nuts 'cause I didn't understand why it was occurring and wasn't able to find good explanation for it. Made my day. Thanks again.

So many benefits to this. I love that it’s in the app… I can build in the view, then materialize as a new dim table. It’s also a great way to learn DAX, and simplify the work your measures have to do in the report :) Love it.

Would be interested to learn more on this in a slower and more detailed format. This seems to be a lot more complex than SQL for the same queries but would be good to know this.

AH HA moment!! I've been having trouble with DAX because I think in SQL...this connects the dots for sure!

Wow, unbelievable quality of the video. The design, transitions and of course, the host! Thank you so much for your work! ❤

Braces {} are important i noticed. Code with light colour on a light background.

Thank for dax studio. If you want to display a list of measures then use the following construct EVALUATE { CONVERT( MAX( 'table'[measure] ), STRING ) & UNICHAR(10) & CONVERT( MAX( 'table'[measure] ), STRING ) }

The timing of this video was uncanny. Thanks so much for this.

Upfront; I have never used PowerBI. And so I'm sitting here thinking why would I want yet another syntax to "replace" SQL? Maybe it's better or faster somehow. Or maybe I can't use SQL in PowerBI. But in the latter case, whouldn't it have been wiser to integrate the classic SQL syntax into PowerBI? I bet it has something to do with the other DAX capabilities.

i dont understand why we even need dax.. sql would be much more seamless imo

Amazing stuff Patrick, I always learn something new from each of your videos

Thank you for the video. This video came right on time. I am attempting to make the mental jump from SQL to DAX and this video is a great help. I'm looking forward to any other trips or tricks you post in the future. 👍🎉🎁

3:40 nice! Didn't know it! 😮

Can you do another video using M like a SQL query? (Power Query is the place I'm most likely to think about data in terms of querying vs DAX is where I'm thinking about building measures)

Thank you!! It's getting close to transact SQL!! AWESOME!!!😊

Awesome video. This has sparked my mind to figure out new ways to use the power of DAX!

Please let me know after getting the results. What should we do, is it only for analysis if we can utilize the results.

It would be awesome if someday in the future you could create DAX notebooks integrated in Power BI Desktop, just like Jupyter Notebooks with Python or similar to RStudio

Awesome video. Planning to use DAX Studio more often, so thank you!

Love this (and your enthusiasm about it). One thing, it sounds a bit echo-y - like the room is very "live".

this is going to be crazy.

Q: I hope if Microsoft comes up with a tool that converts the sql to Dax then would be game changer

Q: Brilliant video, I must say very informative. I write VBA macros but want to get expertise in PowerBI DAX Queries.. Is it right to say that i learn SQL queries and then start my hands on on POWERBI? please advise

I really don't want to talk about how long I have been using Rows() instead of just using the table constructor '{}' that I just learned about in this video.

I still don't understand why we have to write EVALUATE at the beginning of every DAX query. If all queries must begin with EVALUATE, then the interpreter should automatically add it at runtime if necessary.

This was great vid, Patrick!!!

wow this looks amazing, cant wait to try it out

2:35 nice! 😮😮 Didn't know it

This looks amazing, thank you! ❤

Fantastic video!!! All I ever wanted!

Hi, loved the video so helpful. I don't know if you have created one but I run into issues where the dataset becomes so large when pulling into the model, it takes so long to refresh. Do you have any content around optimizing the data retrieval to either get all that data or for a sub-set of that data? Thank you!

Incredible!.. Thanks for sharing

Great feature!! Thanks for sharing.

I would love a sql to dax converter. I'm new to dax and my head hurts.

Is it possible to make DAX code visible (as tooltip eg) for users?

Hello, thank you for the helpful video. I'm encountering a scenario where I require the use of a subquery. Specifically, I need to retrieve all sales from the salestbl where the customers match those in a distinct list obtained from the customer table. However, I'm facing difficulties implementing this query in Power BI due to the presence of date filters in both the inner and outer queries. While SSRS allows the use of date variables for start and end dates, Power BI seems to struggle with the date range in the inner query. Could you provide guidance on how to address this issue using DAX or M-query? Your assistance would be greatly appreciated. Thank you.

Bring in a magic command to DAX where we can chose DAX/SQL

I wish I was cool like Patrick.

Nice! But Dax Studio now have more futures that you need.

I wonder why MS chose this nonintuitive DAX syntax vs just plain sql!

Thank you so much amazing

Hi Guy in a cube, Can I've amazon rds for psql , redshift and crowd twist connect to my same report How many data sources can I connect to my power bi report, do you have a video?

how to use power bi on MacBook Air?

This is bananas! 🍌🍌🍌

Can you use this as tables you create in the model or is the goal of this pure testing and analysis of data?

awesome! as usual you make us very keen to research more on this topic!

#GeauxTigers 🐅

This is cool

Yooooo! So I've been writing DAX as a query language since way back in my SSAS days, when you had to write it in a plain text editor (no intellisense :o) in order to use it in SSRS reports. One question though... I've always used a different syntax to this - partly because TREATAS didn't even exist back in the day. Instead, I wrap my SUMMARIZECOLUMNS in a CALCULATETABLE, which then allows you to pass a psuedo-WHERE clause as a list in the 2nd argument. eg: EVALUATE CALCULATETABLE ( SUMMARIZECOLUMNS ( 'Calendar'[Month], "Total Freight", [M1] ), 'Calendar'[Year] = 2020 ) Is there anything wrong with this alternate syntax? I always found it more intuitive to write my filter predicates as a final step, more like SQL... but I'm the only person I know who seems to do this and have never figured out whether or not my method is egregious.

Beautiful

Interesting

Yo .DAX and SQL Duo.

DAX > SQL because of context & data model

why record with potato..

This is not SQL 😆

No even close to SQL

{TREAT AS} SWEET AZZ

SAR MARKET TO FULLY BULLISH HOGAYA HAI AAJ TO LOSS HOGA AAPKA XD

DAX studio is dead jaja amazing new functionality