Is Power View meant to replace ReportBuilder?

At first glance, it could be easy to confuse Power View and Report Builder. This blog is aimed at helping you to understand the ‘why’ of these packages, so that you and your business can get the best out of these complementary reporting packages.
I do hear complaints now and again, that the Microsoft Business Intelligence reporting packages can offer similar functionality, so it isn’t clear to users whether they are using the best option available to them. The reporting packages, such as Excel, Reporting Services and so on, are aimed at specific users with specific needs. The answer to ‘which package is right for you?’ will depend on the user and the requirements for building and delivering the report, and it is good that there is more than one option.
One way of looking at the ‘Do I use Power View or Report Builder?’ debate is to look at the distinction between a puzzle and a mystery, as specified by Outliers author Malcolm Gladwell. A puzzle can be viewed as a defined question with a defined answer; when all the pieces of the puzzle are in place, then the puzzle is solved. A mystery, however, is more uncertain; we do not have all of the information in place, and the answer can involve surfing lots of ill-defined information in order to get an answer.
Report Builder is aimed at business users who have puzzles i.e. they have the information in place, and the data will give them the answer in the form of a designed chart. A puzzle could be a straightforward question, such as ‘What was our sales for the last quarter, for a specific product?’
Power View is aimed at business users who have a ‘mystery’ to solve. The question could be ill-defined i.e. ‘how do I find out the characteristics of the data?’ or ‘are there any anomalies in the data?’ The question could start off as a puzzle, answered quickly in Power View- but then it could spawn mysteries. So, we go from ‘what’ to ‘why?’ by looking at the data from different angles. 
My perspective in this is that options are always a good thing, particularly if it means an opportunity to learn something new. I’m aware that Power View is a new package for people, given that it’s available in SQL Server 2012. I’ve written this blog in order to help people to understand the ‘positioning’ of Power View in relation to its older cousin, Report Builder.
Power View
Power View is easy to use, and quick. It involves very little typing, and assumes that the underlying data model is correct. It does not require programming language.
Instead, it simply requires you to drag and drop, and it means that you are only ever a few clicks away from the data representation that is available to you. It is easy for data analysts to produce reports that help you to  produce ‘ad hoc’ reports. In other words, it does not require you to know a ‘set’ question to answer, before you start. It helps you to work with an unknown query definition, or workload. The point is that it helps you to ‘surf’ the data without a need for structured reporting requirements.
Report Builder
Report Builder is also easy to use, and is aimed at producing reports quickly and easily. Again, it is not aimed at report writers with programming knowledge. Instead, it is aimed at information users and analysts who require reports quickly. Report Builder helps you to work with known query definitions, or workloads, to produce a defined report. Report Builder can help you to surf the data to a degree, too, but it is mainly for structured reporting.
Although Report Builder has been available since SQL Server 2005, there are some interesting new features added in SQL Server 2012 RC0 for Report Builder. It’s no surprise, for example, the Word and Excel renderers are compatible with the latest version of Excel and Word 2010. This will only work, however, if the Microsoft Compatibility Pack for Word, Excel and PowerPoint pack is installed.
Report Builder is part of SQL Server 2012 RC0, and earlier versions can be found in SQL Server 2005 and 2008. In 2012, it comes in two versions: stand-alone, and ClickOnce, which is available in both SSRS native and Sharepoint integrated mode. In the stand-alone method, it needs to be installed on the computer, and it can be downloaded from here. The ClickOnce version is installed as part of the SQL Server 2012 RC0 installation sequence, and can be started from within Sharepoint or via Report Manager. In Sharepoint, it is nice to see that Report Builder reports are just seen as ‘Documents’ and you’ll be able to create one by selecting ‘New Document’ from the Sharepoint library.
On the other hand, Power View is solely part of Sharepoint Enterprise and SQL Server 2012. 
To summarise, both applications:
Easy to Use
Aimed at Information Workers
Report Builder:
Can be obtained from outside Sharepoint
Emphasis is on a straight reporting tool rather than an analysis tool
Power View:
Is only available in Sharepoint Enterprise
Is only available in SQL Server 2012

To answer the question, the packages support and complement one another; Report Builder isn’t meant to be replaced by Power View, but offers a slightly different perspective on easy-to-access structured reporting.

I hope that helps. As always, any questions, please do leave a comment. 

5 thoughts on “Is Power View meant to replace ReportBuilder?

  1. Hi Jen, Great explainations. Is Power View only available at specific SQL Server 2012 editions as well or it contains in SQL 2012 express edition too.

  2. I hope this doesn't confuse things- I definitely agree that Power View sits alongside Report Builder 3 onwards, but perhaps it does away with the need for Report BUilder 1? Report Builder is a nice Office interface for those that don't like Visual Studio (or where you don't want to install BIDS for information workers), and makes SSRS reports, and Power View is allow about data discovery and telling a story with that data.
    But I think Power View kind of replaces the not-much-loved (and in SQL Server 2008 R2, still 'current') Report Builder v1. Power View is great for ad-hoc reporting, with a couple of caveats, and I don't see a need for Report Builder 1 any more, where previously if you wanted simple drag and drop reports in the MS BI stack, you were stuck with it.
    Power View is lacking a range of export formats and a bit more configurability would be nice, but I think most simple, quick, ad-hoc reporting needs could be met by Power View rather than Report Builder 1.

  3. @RichB – I'm sorry if the blog wasn't more clear, but I was focusing specifically on SQL Server 2012 rather than older versions.

    I was concerned I'd be confusing the issue by comparing different versions of Report Builder since the blog would be about Report Builder 1 / Report Builder 3 and Power View, which would get confusing. For some people, as I've stated, the range of different reporting tools are complex to compare and understand, and bringing different versions into the 'mix' won't help.

    I am trying to keep the blog directed and 'neat' since I've learned my lesson about mixing too many themes in one blog.

    If all your organisation can have is Report Builder 1, then you probably won't be able to look at Power View until you upgrade. That would be the thrust of a topic for a different blog.

    BTW Did I used to work beside you? I'm not sure. I looked at your profile but I couldn't see anything. If it is you, then it's nice to hear from you. If it is a new acquaintance, thank you for getting in touch. Either way, thank you for visiting my blog and for taking the time to comment; new insights are always welcome here.

  4. Hi Jen,
    You're right- your blog post is a lot clearer with the omission of Report Builder 1, and is a very good post. Old style 'report models' are deprecated in SQL Server 2012 and it doesn't come with tools to create or update them, although you can still use them if you've got 'em.

    (P.S. Its Richard Back 🙂 )

Leave a Reply