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

Report parts
Barring small Microsoft .NET-based shops, larger establishments will have more
than one developer and in fact reports are created to be authored and managed in
collaboration with other developers, or report authors. Starting in SQL Server 2008
R2 Reporting Services, the idea of report parts emerged. The idea behind report
parts is to support reuse of parts of the developed reports for improved productivity.
Microsoft developed this by adding the functionality to publish report items to the
Report Servers as report parts to both Native mode and SharePoint Integrated mode
Report Servers. For details follow this link: http://technet.microsoft.com/en-
us/library/ee635721.aspx .
Both Report Designer in SSDT and Report Builder can publish report items as
report parts. In the case of Report Designer, it is one way only. You can publish as
report parts, but you cannot reuse an existing item in report part. In Report Builder,
however, one can work in the collaboration mode suited for more than one report
developer working with report parts. Since data sources depend on the credentials
to facilitate reuse in a collaborative scenario, it is best to use shared data sources with
the credentials stored in the server. When the original report is updated, the reused
report part in another report also gets updated.
Hands-on exercise 5.12 - creating report parts
and reusing an item
The report shown in the next screenshot was created in Report Builder 3.0 using
the Northwind database and a shared data source with the dataset created using
the query after the screenshot: