Working with Report Builder 3.0 - Learning SQL Server Reporting Services 2012 - page 241

Although these considerations are separately listed, they are interconnected. Once
some of these requirements are defined then one begins to come up with a more
detailed plan that needs the source of data (local, SQL Server, cloud, or third party),
the connectivity issues, the delivery type (desktop, Intranet, download, Internet,
cloud application, and so on), the delivery format for hard copies, Web access via
Intranet IIS or through SharePoint, and a multitude of others that are too numerous
to enumerate.

This chapter is not about planning but about using the Report Builder 3.0 tool to
author reports of different kinds that are normally encountered. Of course, there are
others that require custom treatment. SSDT and Report Builder 3.0 have the same set
of tools and most of what you do in one can be done with the other. SSDT is capable
of creating both server- and client-based reports (as related to reporting activity) and
Report Builder creates server (hosted) reports. In addition, SSDT has the full backing
of Microsoft .NET classes that provide programmatic support, which Report Builder
does not provide. This translates to SSDT being used by developers well versed
in Microsoft Visual Studio environment whereas Report Builder aligns more with
report developers and content managers. In Chapter 2 , SQL Server Reporting Services
2012 Projects with Visual Studio 2012 , report authoring with SSDT was covered.

Hands-on exercise 5.1 - creating a report with
an embedded data source
In the following steps, it is assumed that you have installed a standalone version
of Report Builder 3.0 and as the administrator of the computer, you have the
permissions to author reports and in fact, you are a Content Manager . Installing
Report Builder 3.0 also adds a folder shortcut to All Programs as shown here:

1. The Report Builder 3.0 has essentially the same features as Report Builder

2.0, which have been thoroughly described in the article at http://dotnet.
sys-con.com/node/982742 .