The next version of DAX Studio has just been released. You can download this release and read the release notes here
Note: In this release we have updated the versions of the Microsoft ADOMD.Net and AMO libraries we reference to use the SQL 2016 versions. This gives us scope to access some of the new functionality in Power BI and SQL Server 2016, but may mean that you are prompted to download these when you upgrade from a previous version.
Some of the highlights of this release are:
Added an option to trace Direct Query events
There is now an option under File > Options where you can enable extra events in Server Timings for Direct Query based models. These events add extra overhead so you should only enable this option before you start tracing a Direct Query model and you should disable this option once you are finished.
Added Dynamic syntax highlighting
Earlier versions of DAX Studio contained a hard coded list of syntax highlighting keywords and functions. The lists of keywords and functions used for syntax highlighting is now dynamically discovered from the data source. This has advantages when dealing with Power BI in particular which can get new functionality added from one month to the next.
Added rows and KB to server timings tab
Analysis Services 2016 and Power BI have added information to the server timing events that includes information about the number of rows and the size of data returned from each of the timing events. If this information is found it is now surfaced in the server timings tab.
Optimized DaxFormatter calls
The old version of the DaxFormatter.com API required a second call if there was an error to find out the details of the error. The nice people at DaxFormatter.com have updated their API so that this is no longer necessary.
Added an option to specify the default separator style
In the 2.4 release we introduced an option where you could convert on demand between the 2 different separator styles. But all queries had to be executed using the UK/US style.
The UK/US style is where a comma (,) is used as the list and thousands separator and the period (.) is used as the decimal separator.
eg. EVALUTE FILTER( 'Product' , 'Product'[List Price] > 1.25 )
The European/Other style is where a semi-colon (;) is used as the list separator, the thousands separator is a period (.) and the comma (,) is used as the decimal separator.
eg. EVALUTE FILTER( 'Product' ; 'Product'[List Price] > 1,25 )
Now you can choose which style you want to use as your default in File > Options menu.
Added an error message when you attempt to open a .dax file that no longer exists
Prior to this version if you clicked on an entry in your recent file list which pointed to a file that had been renamed or deleted you would just get a blank window with no idea what went wrong. Now there will be an error posted to the output window tell you what went wrong.
- Fixed a bug where server timing traces were also listening for query plan events
- Fixed incorrect removal of square brackets from MDX results
- Fixed a race condition that happened sometimes when trying to capture both Query Plans and Server Timings