Report Builder 2.0 is available from the Microsoft download site.
As I analyze the process of using Report Builder, I will explain how to work with data sources other than those that are represented in the SSRS. While it is possible to create reports that refer to data stored in different sources, this procedure is not intuitive. Given the basic architecture of Report Builder 2.0, users of this product typically create, save, and retrieve reports that are already saved in a given SSRS instance. You can create locally stored reports that use user-provided fixed authentication methods or SSPI-based methods, but these reports cannot be stored in the same SSRS directory – only the file system can store them. Report Builder does not allow developers to refer to SSRS catalogued reports that include user credentials – only reports from publicly available data sources are supported. That is, if the data source authenticates using the Security Support Provider Interface (SSPI), the same credentials are transmitted to SQL Server as if the user accessed the report from a Windows browser window. Note that the connection string defined in the data source must contain the same credentials to access the data. The most important difference between Report Builder and SSRS is that the connection to the database is made through the remote client report processor, not through the server-side SSRS report processor.
However, unlike the SSRS service which returns HTML code to a browser, the Report Processor module of the Report Builder performs these steps on the client system and creates a report in the Report Builder window. This is the same sequence of events that the SSRS handler performs on the server when visualizing simple reports.
when exceptions occur, displays warning dialog boxes for the user.performs built-in queries and passes a set of lines to the report handler combines data with the report layout from the report definition to the RDL.responds to unfilled input parameters by displaying dialog boxes.opens the catalogued data source specified in the RDL file and then opens a database connection to authenticate the user if the credentials are mentioned in the data source.interprets and evaluates the RDL report definition file.opens the selected report in the SSRS directory this RDL file can also be downloaded from the network file system as a second generation RDL file (first and second generation RDL file formats are discussed later).The Report Builder (see figure), like the SSRS report handler hosted on the server, performs the following operations after an end user connects to the report directory of a given SSRS instance: This code is essentially a locally installed report processor written in Report Definition Language (RDL) with a specialized report visualization extension that uses Windows API calls to draw the generated report on the user’s screen (i.e., the report is not passed to the browser as an HTML document). Report Builder 2.0 is based on the SQL Server 2000 Reporting Services (SSRS) code. SSRS Report Builder Tutorial – Creating Your First Report.