After launching a number of really neat self-service business intelligence plugins and components over the past couple of years, Microsoft has finally announced their complete self-service BI package: Power BI for Office 365. Incorporating Microsoft’s four big self-service BI components of the past year or so; PowerPivot, PowerView, Data Explorer and GeoFlow, the Power BI suite combines these parts into a single, unified offering. Most exciting of all though, is the inclusion of a mobile application for either Windows (I’m assuming Win 8) or iPad, which could very well be the secretive “Project Helix”, revealed at last year’s SharePoint Conference. Continue reading “Microsoft announces Power BI for Office 365” »
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” »
The other week, Microsoft announced GeoFlow for Excel 2013 at the SQL PASS Business Analytics conference in Chicago. While it’s not exactly new, it is at least, a pretty impressive looking addition to the data visualisation toolkit.
However, while GeoFlow finally brings 3D geographical visualisation to Microsoft’s self-service BI utility belt (in your face, Batman), it’s hard to make a case for it for any purpose except wowing executives and potential clients.[tube]LNI0r9_BJUM[/tube]
As if renaming the accurately titled Business Intelligence Development Studio (BIDS) to the rather ambiguous SQL Server Data Tools (SSDT) wasn’t bad enough, in December, Microsoft’s latest SSDT release only brought half the expected capabilities to Visual Studio 2012. Yep, the December 2012 SSDT download was missing a key component: the project and item templates for developing MS BI projects in Visual Studio. Thankfully, the newest release (5th March, 2013) has finally added all of the MS BI templates to SSDT, so you can now develop SSIS packages, SSAS cubes and SSRS reports in the Visual Studio 2012 environment.
Unfortunately, they’ve not made the whole process easy. Searching for “SQL Server Data Tools” will likely lead you to a download which, upon installation, will add connectivity and server management tools to VS 2012 – making it like an up-to-date version of SQL Server Management Studio (SSMS), but without the BI project templates.
The latest release (with the BI templates) is actually called:
So make sure that if you’re trying to get SSDT for BI development work, that you download the correct version. Unfortunately, that wasn’t the end of the issues, as I had a bit of trouble with installation that I felt needed sharing.
Begin by downloading the correct installer for the BI enabled version of SSDT from http://www.microsoft.com/en-us/download/details.aspx?id=36843 (782 MB).
Once you execute it, the installer will unpack and run the SQL Server 2012 SP1 setup wizard. Don’t worry about this, remember that SSDT, like BIDS before it, is actually a component of SQL Server based upon the Visual Studio shell, NOT actually an extension to Visual Studio itself.
The trick with the installation is when you reach the Installation Type step (see Fig 1.).
This is because although the SQL Server instance is 64-bit, the Visual Studio 2012 shell is actually 32-bit. If you attempt to upgrade a 64-bit instance with a 32-bit component, it fails the Installation Rules checks and won’t allow you to proceed.
Choosing “New Instance” will work but don’t worry, it doesn’t actually require creation of a new SQL instance, it just allows the installer to get past the pre-installation checks.
If you’ve got a 32-bit instance of SQL Server, it doesn’t matter what option you choose here.
Once the installation has completed (may require a restart), you can open Visual Studio 2012 (or the new SQL Server Data Tools 2012 item on your start menu) and get developing. Click “New Project” in the File menu and check for the “Business Intelligence” templates to confirm that it’s worked.
I’ve yet to find any real differences between the Visual Studio 2012 based SSDT and the Visual Studio 2010 based version that shipped with SQL Server 2012. At the moment, the main advantage of using this release seems to be to take advantage of the improved features of Visual Studio 2012 over its 2010 counterpart, rather than any advancements in the Business Intelligence templates/tools themselves.
They might be there, however, I just haven’t come across them yet. Let me know in the comments below if you’ve spotted any improvements over SSDT 2010 and what they are.