I’ve really been neglecting the blog of late and have been taking a bit of a break from a lot of extra curricular business intelligence and data reading. I figured it was about time to get back to posting though, and as luck would have it, my colleague Stephen came to me with an interesting SSIS performance issue that presented the perfect opportunity for a quick blog post. I’ve not written much about SSIS lately, having been drawn off by the shiny sparkle of developments in the self-service BI sector such as Power BI, and playing with Big Data tools like Hadoop. But I still do a lot of work with SSIS and it’s still my go-to large scale ETL tool. Continue reading “Optimising SSIS to read from a view using OLE DB Source” »
Software and database development articles, tips and discussions.
Just a quick post regarding a strange problem I encountered while working on an SSAS Tabular model project. Built on the same Vertipaq technology as Power Pivot, it’s very easy to get started and produce quick, efficient data models. Unlike Power Pivot, which runs as an Excel add-in, SSAS Tabular models are developed in Visual Studio via the SQL Server Data Tools (SSDT) Business Intelligence add-on. However, once you load up the development environment, it’s almost exactly the same, the only difference really being that when you build a tabular model in VS, it is developed against a temporary cube on a pre-installed SSAS Tabular instance. Power Pivot just works entirely in memory, without requiring an SSAS instance.
The other week I wrote a post discussing how PowerView was the future of SQL Server Reporting Services, and the killer features that made it a compelling choice. Despite the numerous positive advances that PowerView brings to Microsoft/SQL-based reporting, there are of course a number of counter arguments. I deliberately left these out in order to look at some of these reasons in a later post.
As such, here are five reasons why PowerView, despite all its pizzazz, is simply not capable (in its current form) of replacing the venerable SSRS. Continue reading “5 Reasons why PowerView can’t replace Reporting Services” »
Since its introduction with SQL Server 2012, PowerView has started to become the familiar face of Microsoft’s self service business intelligence offering. Its inclusion in Excel 2013 has only reinforced its position as the premier tool for quick, interactive visualisation of data, in conjunction of course with the magnificent PowerPivot. But ask any “traditional” BI developer/architect about Reporting Services (SSRS), and it’s likely that they will staunchly defend it, decrying PowerView as a gimmick.
So here are 6 reasons why PowerView is NOT a gimmick, and may in fact be the future of SQL Server Reporting Services. Continue reading “6 Reasons why PowerView is the Future of Reporting Services” »
Something I see online all the time, is people trying to find a standalone download for SQL Server Management Studio. Until recently, it seems, Microsoft certainly didn’t make it easy to just install the client tools without having to install the entire SQL Server database engine as well. The are plenty of reasons why you might want to install just the client tools and not the database engine on your computer, after all, in this world of self-service business intelligence, it’s no longer just developers and DBAs who are playing with data directly.
Fortunately, with SQL 2012 Express, you have a wide variety of download options, ranging from a standalone version of SSMS Express, to SQL Express (including SSMS), with Reporting Services and Full Text Search.
Check out http://www.microsoft.com/en-us/download/details.aspx?id=29062 to download SSMS as a standalone component.