Problems with specifying a security role while connecting to a Power BI model about daxstudio

[dgosbell]

The problem here is that you are an admin user impersonating a non-admin. So it's an unusual situation. It's probably best to test your role in one query window and run your traces in another

[OmriAvissar]

I want to view the xmSQL code, and trace info, generated by DAX queries under a security role. The purpose is optimising DAX measures.

Is thare a way in which I can manage this using DaxStudio?

[marcosqlbi]

Maybe we should study how to implement this scenario. The problem is that you should use two different processes, but the current implementation of DAX Studio runs the query analysis within the same process (and user) that is receiving profiling events - and that user must be an administrator.

[otykier]

I am facing exactly the same scenario at a client. A handful of measures slow down tremendously when RLS is applied, and I really wanted to look at the xmSQL and query plans. Would I need SQL Profiler to capture the information, when executing the queries as a user with RLS, or is there something we can do within DAX Studio in this case?

[dgosbell]

You could use profiler to capture the Vertipaq SE End events, but this should now work in the 2.9.2 release. I just did a quick double check against the June PowerBI Desktop and SSAS 2017 and I could activate tracing while connected with Role=... and I could see the role predicate pushed down into the xmSQL. Do you have a scenario where this is not working?

[otykier]

I just discovered that I'm not using 2.9.2 yet - how embarassing! Thanks, Darren!