Today we are happy to announce the release of version 3.0.10 of DAX Studio which includes the following fix.
Today we are happy to announce the release of version 3.0.10 of DAX Studio which includes the following fix.
Today we are happy to announce the release of version 3.0.9 of DAX Studio which includes the following fixes and Updates
If you are testing DAX Optimizer you should update to this release as it includes .
This new preview feature enables the ability to collapse sections of a query based on the indenting levels
You can read more about this preview feature here
Today we are happy to announce the release of version 3.0.8 of DAX Studio which includes the following fixes and Updates
If you are testing out the new Fabric Direct Lake mode you should upgrade to this version as it improves the performance of the metadata loading.
Today we are happy to announce the release of version 3.0.7 of DAX Studio
DAX Studio uses an asynchronous, lazy loading strategy to populate the metadata which has worked reasonably well over the years, but we occassionaly see some strange errors due about reader objects being already in use (such as those in issue #1076 ) or responses containing unexpected data. There are actually a number of small tweaks in the previous verion (3.0.6) which were meant to help avoid these issues, but there was also one minor improvement to the formatting of query results which made this worse.
This sort of issue was extremely hard to isolate because I rarely saw it myself and it was very hard to come up with consistent scenarios to reproduce the issue. And if you cannot reproduce an issue you can make changes, but you don't know if you've fixed the problem or if you've just been lucky. It turns out that with some help from some log files from users I was able to isolate and reproduce this issue and confirm that it was a multi-threading bug.
Starting with this version we now internally use a separate connection object for metadata and running queries so this should prevent this issue entirely going forward.
This is a small quality of life improvement where you can now delete entries from the recent server list from the connection dialog itself. This list should be self-maintaining as new entries are added at the top and old one should fall off the bottom over time. But if you have entries that are no longer valid and you want to clean up this list you now have an easy way to remove them.
There are now right-click options on the Log and Results panes to allow you to clear them.
This option will change the behaviour of the export button in the Server Timings tab so that instead of exporting a single json file with the trace data it will export a file for each Storage Engine query that contains the text of each query. This can be useful in scenarios where the enging generates a lot of queries and you want to use another tool like VS Code to quickly navigate between the different files and compare them.
Below is the full list of all the new features and fixes.
Today we are happy to announce the release of version 3.0.6 of DAX Studio
The old Waterfall column has been replaced by the new Timeline column. This column contains the same information as the old waterfall column, but includes a new background image to help visualise times during the execution of a query when either the formula engine (denoted by yellow sections) or the storage engine (denoted by blue sections) was active.
Below is an annotated example of the new Timeline column.
Note that the time that is allocated to the Formula Engine (denoted by the yellow portions of the Timeline) are simply those times during the query when no Storage Engine events were taking place. We do not have separate events for the formula engine activity.
The formatting of the xmSQL code in the Server Timings pane has been improved to include key word highlighting and improved line breaks to make the code easier to read
There are a number of improvements to the output options in this release of DAX Studio
When outputting to a file you now have the option to output to a json format. This output produces the same format as the Power BI ExecuteQueries REST API
When using the custom csv format you can now choose between utf-8 or unicode encoding
There is now a "Formatted File" output option. The standard "File" output is the recommended one as it outputs your data with full precision, decimal numbers are output without any rounding and datetimes are output using a standard ISO 8601 format. However if you require a csv output which uses the same formatting that gets applied to the grid output then this new "Formatted File" option gives you that. Just be aware that if you are transferring these files between machines that you may have issues with datetime data if your regional settings are different between the machines.
This feature is not visible by default you need to turn it on in the Options - Preview settings
The FE Benchmark feature runs a standard formula engine only query against the current data source. It produces a FE Benchmark number that should help in estimating the expected performance in production.
If your laptop runs a query in 2 seconds and it's index is 200, then if you run the same query on a server that has an index 100 we should expect roughly 4 seconds ie. the query will take twice as long since the benchmark score was half.
This option is currently in preview so that we can start testing this across a wider range of real world scenarios. There are a lot of other factors that can influence query performance such concurrent load, CPU cache size and type and the memory and memory bus speeds to name a few. So we may need to look at adjusting this as we gather more real information.
Below is the full list of all the new features and fixes.
Today we are happy to announce the release of version 3 of DAX Studio
This has been an outstanding request for a long time and finally we are happy to announce that we now support Dark Mode! You can switch between the 3 different mode settings using the button at the top of the ribbon
Auto-detect - attempts to set the appropriate mode based off the preferences in the Operating System (should work for Windows 10 or higher)
Light mode
Dark modeWith the help of the amazing Daniele at SQLBI we now have a clean, modern update to the user interface including new icons and visual styling
A couple of important changes worth noting are:
In addition to being able to collapse the ribbon there is now also an option to show a simplified view
This view takes up less vertical space while still keeping the most commonly used features easily accessible.
The internal tracing engine has been re-architected internally which will make it easier to add new trace types in future and it should also have fixed the issue where sometimes the trace data would
In addition the following enhancements have been made to the existing traces:
A "waterfall" column has now been added to the Server Timings tab. This gives you a quick visual indication of which Storage Engine queries took the longest and where they
The Query Plan trace will now show a dashed line to indicate operations that are children of the currently selected row. This
The All Queries trace can now be run in parallel with other trace types. You used to have to either stop other traces or run them in a different document, but now all the different traces can be run at the same time if you need to.
Just take note that traces do add some extra load to the Tabular Engine, so it's a good idea to stop them when you have finished collecting the data you needed.
A new View As option has been added in the Advanced tab to enable easy testing of RLS roles
This enables for both testing the functionality of the selected role to make sure queries return the correctly filtered data and you can run Server Timings traces to measure the impact of these roles on your queries.
When it is active the View As option shows a yellow information bar at the top of the query editor. You can exit out of the View As mode by clicking on the X in the right hand side of the information bar
To make performance comparisons even easier a new option has been added to the Benchmark feature which is enabled when you start the benchmark while you have View As active.
When you tick the option to do a second pass the benchmark results will include a second set of columns in the results for those passes where the RLS role was active
The following lists other minor fixes and improvements that have been added since the previous release
Welcome to the DAX Studio blog.
This is an area where we will put content of interest to DAX Studio users