With all the BIML code done and the production scenarios start to emerge, it would be great to have the BIML code automatic expanded and create new packages if there are changes to the underlying metadata. Either configured manually or directly from the sources. With the MIST application from Varigence – this is possible through the command line util that ships with the installation.
In these times of datawarehouse automation and fast track SSIS, BIML has become a huge contributor to my daily work. On one of my most recent projects we had a custom script task that we needed to implement in the same package several times.
The Power Query tool has just been updated and there are some pretty neat features rolled out: New Transfomation: Use Headers as First Row. Column Name field in Merge Columns dialog. Quick Access Toolbar in Query Editor dialog. Warning for stale data previews in new queries. Function Invocation from Search. Preserve Excel Number formats in the worksheet on query refresh.
On several occasions I’ve been assigned the task to split a delimited string into rows. I’ve done this in different ways, but never thought about the performance or stability of the different approaches for doing this. So here’s my 25 cents and findings.
I came across a colleague of mine, who asked me if the new updatable columnstore index and ROLAP partitions in a Multidimensional cube is the new trend of fast and no-latency Business Intelligence. Well – here is my 25 cents.
One of my longterm customers had a database-server crash a while ago. The server would not spin up after reboot. The whole installation including tweeks and other stuff had to be re-attached to a new and fresh installation of SQL Server 2012. It was s fairly young BI-server, so the damage was not that big after all. Untill today…
Three days of SQL Server Deep dive and new trends in Stockholm, SE. The sessions have been held and the impression will last a while – at least for me. Day 1 – The precon ‘Data Warehouse modelling – making the right choises’ by Davide Mauri (site|blog|twitter) and Thomas Kejser (blog|twitter) was a very good walktrough of the aspects, seen from a architectural angle, of building a data warehouse.
In every project on Business Intelligence there comes a time when the code needs to be deplyed to the production environment. No more development, no more manual work. But what about the partitions on the tabular cube? Do we really need to tell and learn the DBA how to handle that on a periodic plan? The answer is simple: No!
Ever had that awesome SQL tracer build up that does just the right thing for your system – well I know that I had. And someday you might need just the same trace again. But now you need to build it again… Here comes the feature Extended Events in place. It was first introduced in the SQL 2008 version. The feature is a good and lightweight event-driven mechanism for collecting information about your SQL server.
To make a long story short – Do not use formatting in MDX when using results for Reporting Services. Here’s a little tip for all who works with MDX and gets stuck on the performance. Sometimes when you work on MDX queries the performance is very slow. This even though the resultset is only a few rows. (I know that the dataintegrity also is a role player here…). But but, I’ve come up with a little finding. If you have used formatting directly in your MDX query in order to get the whole thing done from the SSAS servers power, […]