WiseOwl Training - Established 1992 Wise Owl Training

Established May 1992
30 years in business
Wise Owl Training
30 years in business
See 527 reviews for our classroom and online training
Which should you learn: Report Builder or Reporting Services?
Part three of a four-part series of blogs

Report Builder and SQL Server Reporting Services are almost identical - which makes the small but important differences even harder to explain.

  1. Should you learn Report Builder or Reporting Services?
  2. Why Report Builder might be better than Reporting Services
  3. Why Reporting Services is better than Report Builder (this blog)
  4. The Wise Owl Recommendation

Posted by Andy Brown on 16 February 2018

You need a minimum screen resolution of about 700 pixels width to see our blogs. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.

Why Reporting Services is better than Report Builder

Although Report Builder is superficially easier to use, you'll quickly discover that actually SSRS is more user-friendly.  Here's why!

Intellisense when creating expressions

For some bizarre reason, Report Builder doesn't show any help when you're typing in expressions:

Report Builder expression

Compare this with the SSRS version below.


By contrast, the Intellisense in SSRS is very good:

SSRS expression

Exactly the same dialog box doing the same thing, but in SSRS.

This single difference almost justifies choosing Reporting Services over Report Builder on its own!

Better query designer

The query designer in Reporting Services is what I'd expect to see, and is similar to the one in Access, Management Studio and Excel Query Builder:

SSRS query designer

Designing a query in SSRS.

Here's someone trying to create the same query in Report Builder:

Report Builder query designer

The button to add a relationship linking the film and director tables is circled.

What were Microsoft thinking of?  I've just counted, and it took 14 mouse clicks to create a link between two tables (and even then I couldn't see this link visually on screen).

Ability to work on multiple reports

Report Builder is very much a one-report package: you can only work on a single report at time.  By contrast, in Visual Studio you can have as many reports open as you like:

Multiple reports

Here I've got 3 reports open simultaneously for editing, and can copy and paste between them.

You can see all of your reports in one go in a window called Solution Explorer:

Solution Explorer

To open a report, just double-click on it.


One other advantage: you can work on a number of reports on your own computer, then deploy them all in one go when you've tested them.

Selectable objects in the Properties window

Here's the properties window in Report Builder:

Report Builder property window

Note that there is no drop down for changing the selected item.


Here's the same window in SSRS:

SSRS properties window

You can click on the drop arrow next to any object to change what is currently selected.


This is only a small thing, but again, it does make you wonder: why?

Pre-filled reports

When you create a report in Report Builder, it comes with a couple of irritating text boxes:

Report Builder blank report

The first thing I always do is delete the header and footer text boxes.

OK, I'm scraping the bottom of the barrel now - time to stop!

This blog has 0 threads Add post