Subscribe: Darren Gosbell [MVP] - Random Procrastination
Added By: Feedage Forager Feedage Grade B rated
Language: English
darrengosbell archive  dax studio  dax  file  new  originally posted  query  release  server timings  server  studio  trace 
Rate this Feed
Rate this feedRate this feedRate this feedRate this feedRate this feed
Rate this feed 1 starRate this feed 2 starRate this feed 3 starRate this feed 4 starRate this feed 5 star

Comments (0)

Feed Details and Statistics Feed Statistics
Preview: Darren Gosbell [MVP] - Random Procrastination

Darren Gosbell [MVP] - Random Procrastination

Business Intelligence, SQL Server, .Net, Powershell and MDX Madness

Copyright: Darren Gosbell

DAX Studio 2.7.0 Released

Mon, 02 Oct 2017 09:57:10 GMT

Originally posted on: major change in this version is to the tracing engine. We’ve introduced a new trace type and made some changes to the way the tracing windows operate and incorporated some enhancements to crash reporting and enabling logging.We've also finished moving off our old codeplex home onto http://daxstudio.orgChanges to the way trace windows workPreviously when you clicked on a trace button, the window opened and the trace was started and when you switched off the trace the window closed. The running of the trace and the visibility of the window was closely linked. In v2.7 we have removed that tight linkage, when you click on a trace button the window opens and the trace still starts as it used to, but when you switch off the trace the window now remains open. The table below shows the 2 new states that trace windows now have. v2.6 and Earlier V2.7 or laterWindow Visible - Trace RunningN/AN/AWindow Closed – Trace Stopped Window Visible - Trace RunningWindow Visible – Trace Paused **Window Visible – Trace Stopped **Window Closed – Trace Stopped All trace windows now have a number of additional controls in their title area.  Starts a paused or stopped trace  Pauses a running trace  Stops a running trace   Clears any information captured in the current trace windowThe tabs for the traces now also have an indicator to show their state so that you can see the state of a given trace at a glance. In the image below you can see that the All Queries trace is stopped, while the Query Plan trace is running and the Server Timings trace is paused. Note that while a trace is paused the server side trace is still active it’s just the DAX Studio UI that is paused, so expensive trace events like Query Plans can still have an impact on the server.The other side effect of this change is that if a .dax file is saved while a trace window is open, when that file is re-opened the trace window will also re-open with the saved trace information, but now the trace will be in a stopped state (previously the trace would open and re-start). This prevents accidentally overwriting the saved information and also means that the saved trace information will open even if you cancel the connection dialog (which would not happen in v2.6 or earlier, cancelling the connection would cause the saved trace information not to open) The “All Queries” traceThe new trace type is called “All Queries” – which captures all queries against the current connection, regardless of the client application. This is useful for capturing queries from other client tools so that you can examine them. When the trace is active it will capture all events from any client tool. The screenshot below shows a capture session that was running against a PowerBI Desktop file. When you hover over the queries the tooltip shows you a larger preview of the query and double clicking on the query text copies it to the editor The “All Queries” trace has a few additional buttons in the title bar area.The following button in the trace window title will copy all the queries matching the current filter to the editor pane.The Filter button shows and hides the Filter controls, the clear filter button will clear any filter criteria from the filter controls. Filters can be set for a specific type of query DAX/MDX/SQL/DMX, for a duration range, username, database or query. The filter all do a “contains” style search that matches if the text you type is anywhere in the field. Note: You cannot have the "All Queries" trace running with either the Server Timings or Query Plan traces as DAX Studio currently only runs one trace session per query window and these traces apply different filters to the trace events. We expect that the normal workflow would be to run the All Queries trace and collect a set of queries. Then you will stop the All Queries trace and look at the long running queries, maybe re-running some of the captured queries with one or[...]

DAX Studio 2.6.0 downloading issues

Wed, 21 Dec 2016 23:06:22 GMT

Originally posted on:

UPDATE: Looks like the 2.6.0a release on codeplex is now being flagged by Chrome as malicious. I don't know if it's the file or that is the issue (our older releases with thousands of downloads appear to now be falgged as "malicious" too now). So I have also made the setup file available as a release from our github repo too -

If you had trouble dowloading the 2.6.0 release yesterday there is now a new 2.6.0a release up at

Yesterday's release of DAX Studio 2.6.0 started off OK. We've had over 400 downloads, but then at some point the browsers seem to think the installer was a malicious file. We're not sure why, but all of them have started throwing up warnings, Chrome seems to be the worst offender, saying that the file is malicious and only giving you the option to discard it


And both Firefox and Edge give you very scary warning, but will let you download the file.

The advice on the Chrome "learn more" link is very generic and there does not appear to be any way of submitting for a re-assessment of this judgement.

I checked both the original file and then downloaded the file from codeplex and checked again (just in case something had infected the file after it was uploaded to codeplex) using Googles site and both times 0 out of 55 antivirus scanners reported any issues.

If you are curious below is a link to the results showing the detailed results:

(image) (image)

DAX Studio 2.6.0 Release

Tue, 20 Dec 2016 23:02:00 GMT

Originally posted on: seem to somehow have gotten into the habit of doing pre-Christmas releases every year, so why break with tradition now :) The latest release of DAX Studio has a couple of new features as well as a bunch of small fixes. The biggest single feature is the support for multiple result sets. Both SSAS 2016 and Power BI support sending multiple EVALUATE statements in a single batch. You can now do the same thing in DAX Studio and we will generate a numbered tab for each result set. We've changed the Connection dialog so that connection types that are unavailable are just disabled instead of being hidden. There is also a little help icon with a tooltip which indicates why the particular option is disabled to help those that are new to DAX Studio. We've added the ability to connect to SSDT Integrated Workspaces. There is now a setting under File – Options to allow you to opt-in for notifications of pre-release builds. So when you launch DAX Studio if there is a new pre-release version available you will get a toast notification. I don't think we will always do a pre-release build, but there have been a number of times where it would have been nice to get a few more people testing out new functionality before doing the final release. When querying measures the Formatting from the data model is now applied. Note that to do this we look for matches between the column names in the result set and the measures in your model. So if you use functions like ADDCOLUMNS or SUMMARIZE you need to make sure to give the output columns the same name as the underlying measure if you want formatting applied. And there have been a bunch of minor enhancements: A link has been added to the dowload page from Help - About when a newer version is available. Added parsing of record counts in Server Timings for SQL 2016 / Power BI Desktop. Improved metadata search performance and the search box now stays open when it has keyboard focus. There are also a number of fixes in this release, some minor, but some also address some annoying crashes: Fixed an issue where Query Plans and Server Timings would not start when connected PowerPivot. Fixed an error when using the locale setting in the connection dialog Fixed an issue with hidden animations running causing background CPU usage even when the app was idle. Fixed crashes when refreshing metadata (also affects the automatic refresh when switching back to DAX Studio after editing your model). Fixed PowerPivot connections so that they stay connected when you open another Excel file. Fixed blank column headers in the results when running DMV queries Fixed file outputs, csv and tab had been switched [...]

ProcessAdd bug in AMO 2016

Sun, 13 Nov 2016 22:26:15 GMT

Originally posted on:

I saw the question below on the MSDN forum about processAdd not working in AMO 2016 and I thought it sounded strange so I did some investigation:

When I ran Redgate Reflector over the Microsoft.AnalysisServices.Core.dll I came across this little gem:


Where it checks if the object is of a type IQueryBinding from the Miocrosoft.AnalysisServices.Core namespace and as far as I can see nothing currently implements this interface. What this means is that if you pass any of the built-in binding classes to the Process method - it will always throw a NotImplemented exception. 

I've posted a bug here and apparently it's a known issue and a fix is already in the pipeline. However there is also a relatively simple workaround which involves creating a class which implements IQueryBinding in your own project.

The IQueryBinding interface is thankfully not that complicated and a full implementation is outlined below:

public class MyBinding : Microsoft.AnalysisServices.Core.IQueryBinding
        public MyBinding(string dataSourceID, string queryDefinition)
            DataSourceID = dataSourceID;
            QueryDefinition = queryDefinition;
        public string DataSourceID { get; set; }
        public string QueryDefinition { get; set; }
        public ISite Site { get; set; }
        public event EventHandler Disposed;
        public void Dispose() { }

You can then simply create a MyBinding instance and pass this in to the Process method for you your partition:

var qb = new MyBinding("Adventure Works DW", "SELECT * FROM table");
partition.Process(ProcessType.ProcessAdd, qb);

(image) (image)

DAX Studio 2.5.0 Release

Wed, 19 Oct 2016 19:46:16 GMT

Originally posted on: 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: New Features 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 API required a second call if there was an error to find out the details of the error. The nice people at 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. Bug Fixes 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 [...]

DAX Studio 2.4.1 Released

Mon, 25 Jul 2016 20:37:23 GMT

Originally posted on: next version of DAX Studio has just been released. You can download this release and read the release notes here Some of the highlights of this release are: Toggle Delimiters A toggle delimiter feature has been added to switch between regional settings styles (commas vs semi-colons). Currently queries still need to be executed using the "US" style comma delimiters, but if you have expressions using semi-colon delimiters then you can easily switch back and forth. This can also be handy if you find an example expression online that is using different delimiters than what you have in your model. this will swap between using comma delimiters and semi-colon style delimiters Intellisense Improvements Added a Function Insight tooltip to intellisense which willl appear after the opening bracket for a function that will show the parameters for a function as well as it's description The loading and caching of intellisense data has also been vastly improved. The slightly delay when starting to type a query against a large model should be gone and you should also not see issues when trying to edit a query in a window that is currently executing a query. [...]

DAX - Creating a measure for Top 5 and Others

Sat, 04 Jun 2016 05:38:07 GMT

Originally posted on: when you have a requirement to show a measure for the TopN of a given attribute the users will want to see the subtotal of all the other items.With multi-dimensional cubes and MDX you can create calculated members in a dimension. But you can’t do this in a tabular model using DAX . You could create a calculated column, but then your TopN would be fixed and could not respond dynamically to changes in filters as calculated columns are calculated and stored at processing time.So one way to make this work is to have a placeholder row (or rows) with "Others" in the table which you are doing the TopN over.The first step in this technique is to create a Rank measure (this saves having to re-type the rank logic multiple times). In this example I’m doing a top 5 Brands.Brand Rank:=RANKX ( ALL ( Brand[BrandName] ), [Sales Amount] )Then we create a top 5 measure that returns the sales amount if the rank is less than or equal to 5 and will return the sum of all ranks if the current brand is "Others" otherwise it will return BLANK()Top5 := IF (     [Brand Rank] <= 5,     [Sales Amount],     IF (         HASONEVALUE ( Brand[BrandName] ),         IF (             VALUES ( Brand[BrandName] ) = "Others",             SUMX ( FILTER ( ALL ( Brand[BrandName] ), [Brand Rank] > 5 ), [Sales Amount] )         )     ) ) Then if we create a pivot table with this measure we get the following result. In the picture below I’m showing the raw Sales amount so you can see how the amounts get re-assigned in the Top5 calculation.This also works as you change the pivot table. When we introduce the Segment on the rows we can show a figure for “Others” within each segment. (Note that for this to work I had to create 2 placeholder “Others” rows, one in each segment). There is a link at the bottom of this post to the file that these screenshots were taken from. At this point, I’m pretty happy. It seems to be working well although calculating ranks is rather expensive so I’m wondering how it will work against larger data sets. I know that there are definitely ways to make this faster if you are using the current generation of DAX engines (Excel 2016, Power BI or SQL 2016) as we have access to things like variables and the INTERSECTS function which we could use in conjunction with TOPN. But I think there are also opportunities to make this faster with “v1” DAXRunning this algorithm against the Adventure Works Product Name column results in a performance profile like the following (using the server timings feature of DAX Studio)Which shows 86% of the time being spent in the formula engine. I’m pretty sure that a fair bit of this time is spent calculating ranks greater than 5 for the “Others” calculation. So I thought it might be faster to a TOPN in descending order and get everything except for the first 5. The formula for that is the followingTop5v2 := IF (     [Brand Rank] <= 5,     [Sales Amount],     IF (         HASONEVALUE ( Brand[BrandName] ),         IF (             VALUES ( Brand[BrandName] ) = "Others",             SUMX (                 TOPN (                     COUNTROWS ( ALL ( Brand[BrandName] ) ) - 5,                     ALL ( Brand[BrandName] ),                     [Sales Amount], 1                 ),                 [Sales Amount]             )         )     ) ) The modified version of the calculation has a much better performance profile, taking about 1/3 of the time and with an almost 50/50 split between the Formula Engine and the Storage Engine.You can download the a sample workbook with these for[...]

Dax Studio 2.3.2 released

Tue, 03 Nov 2015 00:10:11 GMT

Originally posted on: latest release includes a lot of UI polish features and we also now have support for SQL 2016 and Excel 2016 which is mainly an update to the installer and some changes to the Query Plan and Server Timings features to deal with some changes to the xmlSql that comes back in the trace events. Following the theory that a picture is worth a thousand words – below are screenshots of the changes in this release. The File –> Open menu now includes a list of recently opened files. For performance testing you can now set the run button to always doe a clear cache before executing a query. This mode is easily selectable using the new arrow menu on the run button. The model dialogs all have updated styling and now including a shaded overlay so that the active portions of the screen are clearly visible. An options pane has been added to the File menu for setting global program options A Query History pane has been added which records all of the queries run by Dax Studio. If you have the Server Timings feature enabled the Server duration and the FE / SE timing are also tracked. You can double click on an item in the query history to insert it back into the editor. This is great for performance tuning as you can easily see which variation of the query was fastest and returned the expected number of rows and then bring it back into the editor. The metadata pane now loads asynchronously. In earlier versions the loading of the metadata pane was a blocking operation and the user interface could go unresponsive for a short time while loading large models. Now the metadata is loaded on a background thread so the interface remains responsive and the pane that is updating is greyed out to indicate that the load is still in progress. . The new “Define Measure” feature, which is a right-click option on a calculated measure, is a great way to either see how a measure was defined without opening up the whole model. Or you can use it as a starting point to test some variations on the logic. There are also a number of small bug fixes and tweaks and a number of issues that were raised on codeplex that have been fixed (we always tag closed issues with the release they were fixed in) [...]

DAX Studio 2.2.6 released

Thu, 23 Jul 2015 21:27:49 GMT

Originally posted on: release an update to DAX Studio bundling up the following fixes and enhancements: Support for the upcoming release of Power BI Desktop Dynamic Ribbon resizing Remembering of Window size and location fixing display of hierarchies in Excel 2013 fixing quoting of keywords in table names fixing an error when duplicate column names are returned in a query fixing an issue when changing databases when connected to a Multi-Dim server fixing an issue when connecting as a non-admin I’m particularly happy with the dynamic resizing that is part of the Fluent.Ribbon control. It took a bit of effort to figure out, but it provides a much better experience than having to scroll the ribbon when window size is reduced. So on a wide screen display you still get the full ribbon in all it’s glory Then on an older 1024px wide screen a few of the labels in the Edit and Find groups drop off Then things dynamically shrink then the groups finally start to collapse into dropdown menus. So if you want to go split screen on a small display everything still works even at 500px wide without needing to scroll the ribbon. [...]

Announcing DAX Studio 2.2.0

Tue, 23 Jun 2015 20:58:25 GMT

Originally posted on: we released DAX Studio 2.2 which includes a number of big enhancements. You can download the new release from Below is an outline of the new functionality you will find in this release. Intellisense DAX Studio now has intellisense support, it's a fairly basic implementation, but I think I've got it working fairly smoothly. Note that it’s based on the best practice of always prefixing columns with the tablename and never prefixing a measure with a table name. So if you type ‘table name’[  you will get intellisense for all the columns in the ‘table name’ table. But if you just type [ you will be presented with a list of all the measures in the model. The intellisense brings up table, column and measure metadata information from the current model: As well as functions and keywords, including the descriptions for functions. The function metadata is coming from the DICOVER_FUNCTIONS dmv so it should accurately reflect the capabilities of the current data source (So you will see some additional functions when connected to newer data sources such as Power BI Designer): Tracing (Query Plans & Server Timings) One of the most significant new features is support for the tracing features (Server TIming & Query Plans) against PowerPivot. This has involved a significant amount of work re-building the internal code which handles this, but the end effect is that the Query Plan and Server Timings buttons are now enabled when connected to a PowerPivot model.  We've also altered the layout of the server timings information I found when I was reading the results that I was always comparing Total Duration vs Total CPU and comparing the ratio of these two figures, so I've added a little "parallelism factor" under the Total CPU. I also found that I was looking to compare FE vs SE duration and the number of SE Queries to the number of SE Cache hits, so I've moved them onto the same lines. Support for Multi-Dimensional SSAS Servers Although it’s a little bit of a novelty, DAX Studio now properly supports connecting to multi-dimensional servers. This kind of worked previously if the default database for your multi-dimensional instance only had a single cube, but threw an error if it had multiple cubes. I’m now injected in a CUBE= parameter in the connection string when connected to a multi-dimensional server so this should no longer be an issue. Support for Multiple Power BI Designer instances We now have support for multiple instances of Power BI Designer, so if you have more than one copy of the designer open you can see the names of the .pibx files that you have open and choose which one to connect to. Highlighting of unnatural hierarchies Unnatural hierarchies can have a negative impact on performance so we highlight those in the metadata pane. Bug Fixes There have been a number of minor bugs that have been fixed along the way, including a number that were not officially reported, but were discovered during testing. FIXED - Doubling up of backslash characters when using DAX Formatter FIXED - Unable to connect to SSAS servers when not an administrator FIXED - changing the connection for a query window would sometimes throw an error FIXED - source database changing on metadata refresh when connected to a SSAS server FIXED - cannot connect to a PowerPivot model where the file path contains single quotes Known Issues The following issue which was first identified in 2.1.1 still remains: "Linked Table" output for the Excel add-in only works for PowerPivot models if there is at least one table in the model that was created by linking data from an Excel table. We [...]

SSAS Tabular–per table LastProcessed dates

Wed, 13 May 2015 11:52:43 GMT

Originally posted on: saw a question yesterday on the MSDN forums ask how to go about exposing the LastProcessed datetime per table. Marco has a great post here ( about a number of ways to get the last processed date at the database level. But none of these techniques work at the table level. Having a look through the various DMVs that are available and none of them seemed to have this information apart from DISCOVER_XML_METADAT which returns a large XML document which can be tricky to query. However the information in this DMV is also used to populate the AMO object model. So it should be possible to use AMO to pull out the last processed datetime per table and then push it in using a variation of the processAdd push mode processing. I started by creating a new table in my database called LastProcessed using the following query as a source SELECT CAST('' as varchar(256)) as TableName, Getdate() as LastProcessed WHERE 1=2 This generates an empty table with a string column and a datetime column which will be the target for our processAdd push processing. I was not exactly sure how to construct the XMLA for the processAdd command so I create a simple SSIS package using a Dimension Processing Destination in a DataFlow task and captured the XMLA it produced using SQL Profiler. The command that Profiler captured was missing the section that you would use for pushing a batch of data so I adapted one of Greg Galloway’s excellent XMLA processAdd examples and then wrapped that in a powershell script. The powershell script I created can be found here And can be run with a simple command like the following: .\update-ssaslastupdated -serverName "localhost" -databaseName "advwrksLastProcessed" -tableName "LastProcessed" Once that succeeds you can either expose the whole table or you could hide it and build measures to just expose the dates for specific tables. Below is an example of querying this table in my adjusted Adventure Works database. You can see that ‘Internet Sales’ and ‘Reseller Sales’ have been processed at different times to the other tables in the database. [...]

BIDS Helper 1.7.0 released

Thu, 23 Apr 2015 21:02:49 GMT

Originally posted on: few days ago the BIDS Helper team released of v1.7.0 which you can download from here: This version comes with a few bug fixes, and some new functionality, but the most significant enhancements are to the BIML Engine thanks to our friends at Varigence. I’ve copied and pasted the release notes below. Note that there are some possible breaking changes in the new BIML Engine, so if you have existing BIML script please read this section carefully. ====== Release Notes ======= Fixed Issues: Fixes to all features so they work when the project is inside a solution folder. Fixed Biml project connections in Visual Studio 2013. Reports launch in the proper version of the Report Viewer control in Visual Studio 2012 and 2013. Improvements Biml updates to bring it up-to-date with Mist 4.0 Biml updates to support emitting SSIS 2014 packages from Visual Studio 2013. Biml brings the Output window to the front, displays a progress bar, and displays a more useful errors dialog Enabling the ability to add a translation for the default language in Tabular Translations Editor to makefrictionless renaming easier. Improvements to Tabular Actions Editor: Adding button to test all MDX expressions ensuring the drillthrough column dropdowns only show columns from related tables Adding a button to let you copy an existing action Adding a button to populate the drillthrough action columns with all columns in related tables (since it's quicker to manually delete than manually add columns from this list) Allowing MeasureGroupMeasures to apply to any action type Printer Friendly Dimension Usage for Tabular Biml Details There are a huge number of changes to Biml in this release. Below are highlights of some of the more notable changes and those changes that were most requested by users. BREAKING CHANGES RootNode.PackageProjects has now moved entirely into RootNode.Projects, including all namespaces. This is done to better support other project types such as analysis services projects. The mitigation is to change all instances of the tag to the tag. MITIGATION: If backwards compatibility with older versions of Mist is required, the PackageProjects/Projects element name can be conditionalized based on the tools version. Removed QuerySource and Destination. These were abstractions that wrapped OleDbSource/AdoNetSource and OleDbDestination/AdoNetDestination in a single interface that offered the intersection of their features and automatically chose the correct component type to emit based on the referenced connection type. These language elements were not particularly useful, were very narrowly used, and their removal will prevent unintentional use by new customers. MITIGATION: Change any instances of QuerySource or Destination to the appropriate OleDbSource/AdoNetSource and OleDbDestination/AdoNetDestination All instances of the word Hadron have been removed from the project. Most notably, namespaces that included “Hadron” have 1:1 replacements with “Biml” MITIGATION: Empty classes were added in the removed namespaces to prevent code with legacy namespace imports from breaking scripts AstDimensionNode and AstFactNode have been removed. SSAS metadata is now added underneath the AnalysisMetadata element of table objects. This is unlikely to affect most BIDSHelper users, since SSAS emission is only supported in Mist. AnalysisServices connection property OverriddenConnecti[...]

SSRS–adding a pipe delimited text export option in Sharepoint Integrated mode

Fri, 10 Apr 2015 10:37:34 GMT

Originally posted on: are currently looking decommission an old reporting portal based on another technology stack and replace it with SSRS running in Sharepoint integrated mode. However one of the requirements was to support a “pipe delimited” CSV export format. There are a number of posts you can find about changing reportserver.config when running SSRS in standalone mode, but I could not find much information about how to do this when running in Sharepoint Integrated mode. MSDN documentation lists the various cmdlets, but does not show examples of the parameter values which is pretty useless as some of the parameters require XML fragments. This blog got me close and when combined with the information from this one I was able to come up with the following powershell script which does what I needed. You’ll need to run this from the Sharepoint Management Shell (I logged on to the console of one of our app servers to do this) using an account that has farm admin rights. $svrDirectives = @"     CSV (Pipe Delimited) "@ $extConfig = @“     |     false     csv     False     ASCII "@ $typeName = "Microsoft.ReportingServices.Rendering.DataRenderer.CsvReport,Microsoft.ReportingServices.DataRendering" $apps = get-sprsserviceapplication foreach ($app in $apps) {   New-SPRSExtension -identity $app -ExtensionType "Render" -name "CSVPipeDelimited" -TypeName $typeName –ServerDirectives $svrDirectives –ExtensionConfiguration $extConfig } This code loops over all the service applications in the current farm so even if you have a multi tenancy type situation it *should* work. Although if you are in this situation you should do your own testing. Our farm only has the one SSRS service application. [...]

DAX Studio 2.1 Released

Tue, 17 Mar 2015 20:17:13 GMT

Originally posted on: I am pleased to announce the release of the latest update to DAX Studio – v2.1.0 You can get it from the releases page on codeplex: Below is an outline of what’s new in 2.1. A big thanks to Daniele Perilli for his assistance with the graphics and Marco Russo for his work on the Query Plans and Server Timings tabs plus his help with testing this release. UI Refresh Thanks to assistance from Daniele Perilli on the graphics side we now have a lot more consistency in our ribbon and we’ve moved all the buttons onto the Home tab and moved the database dropdown to the metadata pane. This has enabled us to fit all the buttons you’d use regularly onto the home ribbon. Metadata Search We now support searching in the metadata pane. If you hover over the little magnifying glass in the top right of the metadata pane the search control will fly out and as you type the metadata will filter down to only show objects containing the characters you’ve typed. The icon changes to a green colour when a search is active so that you know that you are not looking at the full set of metadata. Search and Replace We now support searching for text within a query document, including highlighting all matching text. And we support replacing of text Both search and replace include the ability to do case-sensitive searches, regular expressions, wildcards and full word matches. These dialogs use the same hotkeys as Visual Studio Ctrl-F for Find and Ctrl-H for Replace. Improved Server Timings Tab We now show a much nicer view of the aggregate timing details as well as showing the detailed scan events with their timings. You also have the option of showing cache and internal events although these are hidden by default. Improved Query Plan tab The QueryPlans are now pre-processed to make them easier to read and the total number of records for each line is split out so that it can be clearly seen and so that you can sort by this column to find the operations which are traversing large numbers or rows. Save Query Results to a File Thanks to the codeplex user mogular who submitted an initial code sample for this feature. You can now export query results to either a comma-separated (csv) file or a tab-delimited (txt) file by choosing the File output option. Using Semantic Versioning for releases I’ve never really had a strict way of assigning version numbers, but I was not really happy with using the full 4 part version that is generated by .Net. So I’ve decided to start using a variation of Semantic Versioning for the releases. This uses a 3 part version number .. where: – gets updated for significant or breaking changes – gets updated for new features – gets updated for fixes to existing features and updates to a higher number reset the lower ones. Fixes There have been numerous small fixes but some of the notable ones are: Excel Add-in Regional Support – there was a bug in v2.0 which caused the Excel add-in to fail to load correctly on PCs that had regional settings that did not use a period (.) as the decimal separator. This has now been fixed and the Excel add-in should work regardless of the regional settings on the PC New Version notification – this was actually silently failing in v2.0 Updates to syntax highlighting definitions Improvements to the Excel “Linked Table” output  Known Issues "Linked Table" output for the Excel add-in only works for PowerPivot models if there is at least[...]

The Care and Feeding of SSAS in Production - SQL Saturday 365 Melbourne

Sun, 01 Feb 2015 19:31:55 GMT

Originally posted on: are not far away from SQL Saturday #365 which is occurring on Feb 7th, 2015. If you live in or around Melbourne it’s worth considering making the effort to come along. We have a great line up of 30 different sessions with speakers from 7 different countries including 16 MVPs. This year I’m doing a talk called “The Care and Feeding of Analysis Services in Production”. I was partly inspired by the “Accidental DBA” topics that I’ve seen people doing for the relational engine and figured it was time someone did something similar for SSAS. I’m going to talk about both Tabular and Multi-Dimensional, so there should be something in there for everyone. Below is the session abstract: A lot of the information you'll find on Analysis Services is focused around the initial creation of databases and models, but once you have a solution deployed to production then what? In this session we will look at what it takes to run an Analysis Services server in production. What are the basics that you need to know about how the server works. Including things like threading, memory usage and locking. How can you monitor the health of your server? What tools can you use to find out what's happening on your server? We'll have a look at what you should be monitoring to make sure your system is running properly and run through what to investigate went things don't run as smoothly as you'd like. [...]