Profiler Trace for Power BI Desktop

Here are the basic steps you can use to run a trace against a Power BI Desktop file.

1-ProfilerTrace

  • This is necessary to trace the SSAS 2017 instance (1400 compatibility level) running in the latest Power BI Desktop versions.
  • Find the Process ID (PID) of the Power BI Desktop File
    • Open Task Manager and find the PID associated with the msmdsrv process
      • See the Details Tab in Windows 10

PID

  • If you have multiple Power BI Desktop files open or SSAS instances running on your local machine you’ll see additional processes
  • Find the Port being used by the Process ID
    • Open the command prompt and enter netstat -anop tcp

POrt

  • The port is under the Local Address column for the SSAS PID
  • Run the Trace from Profiler 17′

ProfilerConnection

  • Server name: localhost: <port>
  • Capture session details from PBI Desktop Queries

ProfilerTrace

  • For example, observe how Report and Page filters are converted into DAX variables and the (relatively) new DAX functions are used such as SUMMARIZECOLUMNS().
  • To go a step further with analysis, copy the DAX query from the Query End Event into DAX Studio.
    • Connect DAX Studio to the PBI Desktop file

DAXStudio

  • Which events to include in the trace or trace template and how to use/analyze the data is outside the scope of this blog post but tracing Power BI Desktop is a great way to understand how features and functionality (e.g. new slicers, new functions) are executed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s