Reporting Services Tools | Microsoft Docs

Reporting Services Tools | Microsoft Docs
Table of Contents
Overview
Reporting Services in SQL Server Data Tools
Design Reports with Report Designer
Add a New or Existing Report to a Report Project
Deployment and Version Support in SQL Server Data Tools
URL Examples for Published Report Items on a Report Server in SharePoint Mode
(SSRS)
Set Deployment Properties
Dock the Report Data Pane in Report Designer
Report Designer F1 Help
Document Outline
Design View
Preview View
Grouping Pane
Project Property Pages Dialog Box
Reporting Services Login Dialog Box (SSRS)
Reporting Services in SQL Server Management Studio
Set Report Server Properties
Connect to a Report Server in Management Studio
Delete an Item
Report Server in Management Studio F1 Help
Cancel Report Server Jobs
Delete Catalog Items
Job Properties
New Shared Schedule
New System Role
New User Role
Schedule Properties (General Page)
Schedule Properties (Reports Page)
Server Properties (General Page)
Server Properties (Execution Page)
Server Properties (History Page)
Server Properties (Logging Page)
Server Properties (Security Page)
Server Properties (Advanced Page)
System Role Properties
User Role Properties
Report Builder authoring environment
Scripting and PowerShell with Reporting Services
Script with the rs.exe Utility and the Web Service
Format a Reporting Services Script File
Run a Reporting Services Script File
Script Deployment and Administrative Tasks
Sample Reporting Services rs.exe Script to Copy Content between Report Servers
Access the Reporting Services WMI Provider
Report Server Command Prompt Utilities
rskeymgmt Utility
rsconfig Utility
RS.exe Utility (SSRS)
Tutorial: How to Locate and Start Reporting Services Tools
Reporting Services Tools
3/24/2017 • 6 min to read • Edit Online
SQL Server Reporting Services contains a set of graphical and scripting tools that support the development and
use of rich reports in a managed environment. The tool set includes development tools, configuration and
administration tools, and report viewing tools. This topic gives a brief overview of each tool in Reporting Services
and how it can be accessed.
To find a tool right away, see Tutorial: How to Locate and Start Reporting Services Tools (SSRS).
Tools for Report Authoring
The following table lists the available tools for report authoring in SQL Server Reporting Services.
TOOL
DESCRIPTION
HOW TO ACCESS
SQL Server Mobile Report Publisher
With Mobile Report Publisher, you can
create mobile reports that dynamically
adjust the content to fit your screen or
browser window and scale well to any
screen size.
Download the SQL Server Mobile
Report Publisher
Create mobile reports on a design
surface with adjustable grid rows and
columns, and flexible mobile report
elements.
For more information, see Create
mobile reports with SQL Server Mobile
Report Publisher.
Power View
An interactive data exploration and
visual presentation experience designed
to let you create and interact with
reports based on Analysis Services
tabular models.
Reporting Services in SharePoint mode.
Browser with Silverlight.
TOOL
DESCRIPTION
HOW TO ACCESS
Report Designer
Use this tool to design reports. Includes
the following features:
SQL Server Data Tools (SSDT)
Deploy to a native mode or SharePoint
mode report server.
Hosted in SQL Server Data Tools (SSDT)
Report Data pane to organize data used
in your report
Tabbed views for Design and Preview
for interactive report design
Query designers to help specify which
data to retrieve from data sources and
that are associated with data source
types in the RSReportDesigner
Configuration File
Expression editor with IntelliSense to
build Visual Basic expressions that
customize report content and
appearance
Supports custom report items and
custom query designers
For more information, see Reporting
Services in SQL Server Data Tools
(SSDT).
Report Builder
Use this tool to design reports. Includes
the following features:
Download the standalone version of
Report Builder
Deploy to a native mode or SharePoint
mode report server.
Or open from Report
Manager/SharePoint
Microsoft Office-like authoring
environmentSQL Server Mobile Report
Publisher
Ability to save report items as report
parts
A wizard for creating maps
Aggregates of aggregates
Enhanced support for expressions
Query designers to help specify which
data to retrieve from a selection of
built-in data sources types
For more information, see Report
Builder in SQL Server 2016.
Tools for Report Server Administration
A set of graphical and scripting tools are available for administering the report server in SQL Server Reporting
Services. The tools that you use depend on the deployment mode of your report server.
Native Mode
The following table lists the available tools for administering the report server that is deployed in native mode.
TOOL
DESCRIPTION
HOW TO ACCESS
Reporting Services Configuration
Manager
Use this tool to configure a Reporting
Services installation. Available tasks
include:
Start menu
Configuring both local and remote
report server instances
Configuring the Report Server service
account.
Creating and configuring one or more
Web service URL.
Configuring the Report Manager URL
Creating and configuring the report
server database.
Configuring a scale-out deployment.
Backup, restoring, or replacing the
symmetric key that is used to encrypt
stored connection strings and
credentials.
Configuring the unattended execution
account.
Configuring an SMTP server for e-mail
delivery.
Note: The Reporting Services
Configuration Manager does not help
you manage report server content,
enable additional features, or grant
access to the server.
For more information, see Reporting
Services Configuration Manager (Native
Mode).
TOOL
DESCRIPTION
HOW TO ACCESS
SQL Server Management Studio
Use this tool to manage one or more
report server instances in a single
environment, including:
Start menu
Managing both local and remote report
server instances
Setting report server properties
Modifying role definitions
Turning off report server features you
are not using
Managing jobs
Managing shared schedules
SQL Server Configuration Manager
Use this tool to:
Start menu
Start and stop the Reporting Services
Windows services
Configure Customer Feedback
Reporting, the dump directory location,
and error reporting
** Warning *\*Do not use this tool to
configure service account. Use the
Reporting Services Configuration tool
instead.
For more information, see SQL Server
Configuration Manager.
Rsconfig Utility
Use this tool to configure and manage
a report server connection to the report
server database. You can also use it to
specify a user account to use for
unattended report processing.
Command prompt
For more information, see Report Server
Command Prompt Utilities (SSRS).
Rskeymgmt Utility
Use this tool to:
Extract, restore, create, and delete the
symmetric key used to encrypt report
server data
Join report server instances in a scaleout deployment
For more information, see Report Server
Command Prompt Utilities (SSRS).
Command prompt
TOOL
DESCRIPTION
HOW TO ACCESS
Windows Management Instrumentation
(WMI) Classes
Use these classes to automate the
configuration tasks in Reporting
Services Configuration Manager
without the need to use the graphical
user interface.
Visual Basic script
For more information, see Accessing the
WMI Provider Programmatically.
SharePoint Integrated Mode
In SharePoint mode, the Reporting Services is a service application in the SharePoint architecture, and is
administered directly through SharePoint
TOOL
DESCRIPTION
HOW TO ACCESS
SharePoint Central Administration
Use SharePoint Central Administration
to create, query, and manage the
shared service applications for
Reporting Services.
Browser to the SharePoint site URL for
Central Administration
For more information, see
Configuration and Administration of a
Report Server (Reporting Services
SharePoint Mode).
PowerShell Cmdlets
Use PowerShell cmdlets to create,
query, and manage the shared service
applications for Reporting Services.
SharePoint 2010 Management Shell
For more information, see PowerShell
cmdlets for Reporting Services
SharePoint Mode.
Tools for Report Content Management
A set of graphical and scripting tools are available for managing content in SQL Server Reporting Services. The
tools that you use depend on the deployment mode of your report server.
TOOL
DESCRIPTION
HOW TO ACCESS
Report Server Web service URL
Use this tool to browse content in the
report catalog in a generic item
navigation page.
Browser
For more information, see Report Server
Web Service.
TOOL
DESCRIPTION
HOW TO ACCESS
Web Portal
(Native mode only) Use this tool to
administer a single report server
instance from a remote location over an
HTTP connection. You can do the
following:
Browser
View, search, print, and subscribe to
reports.
Create, secure, and maintain the folder
hierarchy to organize items on the
server.
Configure role-based security that
determines access to items and
operations.
Configure report execution properties,
report history, and report parameters.
Create report models that connect to
and retrieve data from a Microsoft SQL
Server Analysis Services data source or
from a SQL Server relational data
source.
Set model item security to allow access
to specific entities in the model, or map
entities to predefined clickthrough
reports that you create in advance.
Create shared schedules and shared
data sources to make schedules and
data source connections more
manageable.
Create data-driven subscriptions that
roll out reports to a large recipient list.
Create linked reports to reuse and
repurpose an existing report in different
ways.
Launch Report Builder to create reports
that you can save and run on the
report server. For more information, see
Web portal (SSRS Native Mode).
RS Utility
See Also
Reporting Services Report Server
This tool is a script host that you can
use to perform scripted operations. Use
this tool to run Visual Basic scripts that
copy data between report server
databases, publish reports, create items
in a report server database, and more.
For more information, see Report Server
Command Prompt Utilities (SSRS).
Command prompt
Reporting Services Concepts (SSRS)
Reporting Services (SSRS)
Reporting Services in SQL Server Data Tools (SSDT)
5/30/2017 • 17 min to read • Edit Online
SQL Server Data Tools (SSDT) is a Microsoft Visual Studio environment for creating business intelligence
solutions. SSDT features the Report Designer authoring environment, where you can open, modify, preview, save,
and deploy Reporting Services paginated report definitions, shared data sources, shared datasets, and report parts.
SQL Server Data Tools (SSDT) is not included with SQL Server. Download SQL Server Data Tools.
This topic describes SQL Server Data Tools solutions, projects, project templates, and configurations used for
Reporting Services, and the views, menus, toolbars, and shortcuts that you can use in Report Designer.
To get started designing reports, see Design Reports with Report Designer (SSRS).
Solutions and Projects
A report project acts as a container for report definitions and resources. Every file in the report project is published
to the report server when the project is deployed. When you create a project for the first time, a solution is also
created as a container for the project. You can add multiple projects to a single solution.
Configurations
To create multiple sets of project properties for deployment variations such as enterprise test and production
report servers, use the Configuration Manager. For more information, see Deployment and Version Support in
SQL Server Data Tools (SSRS).
Report Server Projects
When you install Reporting Services, the following project templates are made available in SQL Server Data Tools
(SSDT):
Report Server Project. When you select a Report Server Project, Report Designer opens. A Report Server
Project is a Business Intelligence Projects template installed by Visual Studio that is available from the New
Project dialog box. For more information, see Add a New or Existing Report to a Report Project
(SSRS).Report Server project properties apply to all reports and all shared data sources in a SQL Server
Data Tools (SSDT) project. These properties include the URL for the report server and the folder names for
reports and shared data sources. Use the Project Property Pages dialog box to view the current property
values. To open this dialog box, on the Project menu, click Properties.
Report Server Project Wizard. When you select a Report Server Wizard Project, a report server project is
automatically created, and the Report Wizard opens. In the wizard, you can create a report by following
instructions on each page to create a connection string to a data source, set data source credentials, design
a query, add a table or matrix data region, specify report data and groups, pick a font and color style,
publish the report to a report server, and preview the report locally. After you create a report with the
wizard, you can change the report data and the report designer by using Report Designer in the Report
Server project.
Report Designer Windows and Panes
Report Designer supports two views: Design to define the report data and report layout, and Preview to display a
rendered view of the the report. In each view, you can display multiple windows to help you design or view a
rendered report.
Report Data Pane
The Report Data pane displays built-in fields, data sources, datasets, field collections, report parameters, and
images.
Use the Report Data pane to view:
Built-in Fields Predefined report information such as the report name or the time the report was
processed.
Data sources A data source represents a name and connection to a source of data.
Datasets Each dataset includes a query that specifies which data to retrieve from the data source. Expand
the dataset to view the collection of fields specified by the dataset query.
In some query designers for multidimensional datasets, you can specify filters in the Filters pane and
indicate whether to create report parameters. If you specify the report parameter option, a special dataset is
automatically created to populate the parameter’s valid values list. By default, the dataset does not appear
in the Report Data Pane. For more information, see Show Hidden Datasets for Parameter Values for
Multidimensional Data (Report Builder and SSRS).
Report parameters The list of report parameters. Parameters can be created manually or automatically
when a dataset query includes query parameters.
Images The list of images that are available to include as an Image report item in a report.
Data sources and datasets in the Report Data pane represent the elements in the report definition. The
Report Data pane is a feature supported by multiple report authoring environments. In Report Builder, it is
the only pane available for managing data sources and datasets. In Report Designer, the Report Data pane
works with Solution Explorer, which lists shared data sources and shared datasets as files. Shared data
sources and shared datasets in the Report Data pane must point to their corresponding Shared Data
Sources and Shared Datasets in Solution Explorer. The Report Data pane elements then contain a reference
to the data files in Solution Explorer. The project properties determine whether the shared data sources and
shared datasets are deployed to the report server or SharePoint site. For more information, see Convert
Data Sources (Report Builder and SSRS).
NOTE
If you do not see the Report Data pane, click in the Design area and then on the View menu, click Report Data. If the
Report Data pane is floating, you can anchor it. For more information, see Dock the Report Data Pane in Report Designer
(SSRS).
Grouping Pane
Use the Grouping pane to define groups for a tablix data region. You can define row groups and detail groups for
tables and row and column groups for matrices. You cannot use the Grouping pane to define groups for Charts or
other data regions. For more information, see Understanding Groups (Report Builder and SSRS).
The Grouping pane has two modes:
Default. Use the Default mode to display all row and column groups in a hierarchical format that shows
the relationship of parent groups, child groups, adjacent groups, and detail groups. A child group appears
under and at the next indent level compared to its parent group. An adjacent group appears at the same
indent level as its peer or sibling groups.
Use default mode to add, edit, or delete groups. For groups based a single dataset field, drag the field to the
Row Groups or Column Groups pane. You can insert the group above or below an existing group. To add an
adjacent group, right-click the sibling group, and use the shortcut menu. To display which tablix cells belong
to a group, select the group in the Grouping pane.
Advanced. Use the Advanced mode to display static and dynamic row and column group members of the
selected tablix data region. You must use group members to set properties that control the visibility of the
rows and columns associated with a group or group member, or the rules that renderers use to try to keep
groups together on a page. Group members appear on the design surface as cells in the row group and
column group areas.
NOTE
To toggle between Default and Advanced modes, right-click the down arrow to the right of the Column Groups icon.
For more information, see Grouping Pane.
Toolbox
The Toolbox contains report items that you can drag to the design surface. Data regions are report items that you
use to organize data on the report. Table, Matrix, List, Chart, Gauge, Data Bar, Sparkline, and Indicator are data
regions. Other report items include Map, Text Box, Rectangle, Line, Image, and Subreport. Custom report items
might also appear on this list if they have been installed and registered by your system administrator.
Properties Pane
The Properties pane is a standard Visual Studio window that shows property names and values for the currently
selected report item on the design surface. In most cases, property names correspond to elements and attributes
in the Report Definition Language (RDL) file. The most commonly used properties can be set by using the
Properties dialog box for the selected item. To open the corresponding dialog box, click the Property Pages
button on the Properties pane toolbar. Advanced users can set property values directly in the Properties pane.
Use the Properties pane to:
Set properties for the currently selected item on the design surface. Some properties provide a drop-down
list of values. You can also type the value directly in the cell. Some properties contain a collection of values,
indicated by the value (Collection). Most properties can accept an expression; complex expressions are
indicated by the value <Expression>. Click <Expression> to open the Expression dialog box. For more
information, see Expression Dialog Box.
Use the Properties pane toolbar buttons to change the grid from category view to alphabetical view. In
category view, you may need to expand a category to see all the properties under it. To open an item's
Properties dialog box, click the Property Pages button on the toolbar or by right-click the item and click
Properties.
Set properties for the currently selected group member in the Grouping pane. Group member properties
help control how static group header and footer rows repeat for each group instance. For more information,
see Display Headers and Footers with a Group (Report Builder and SSRS).
To display the Properties pane, from the View menu, click Properties Window. You can undock this pane
and move it to another area of the SQL Server Data Toolswindow, or display it as a tabbed view on the
design surface.
Solution Explorer
Solution Explorer is a standard Visual Studio component that displays all the items in your project. For a Report
Server project, this includes folders to organize shared data sources, shared datasets, reports and resources. Folder
items are automatically alphabetized when you open the solution file. To view item properties in the Properties
pane, select the item.
Output
The Output window displays processing errors when you preview a report, and publishing errors when you deploy
a report or a shared data source.
Use the Output and the Document Outline windows to help debug errors in expressions.
Document Outline
The Document Outline window displays a hierarchical list of all report items in the report definition. To open the
Document Outline pane, from the View menu, point to Other Windows and click Document Window.
Use the Document Outline pane to help identify text boxes and other report items by name. When you select an
item in the Document Outline, the item is also selected on the Design Surface.
Task List
The Task List window displays build errors for unsupported features when you import a report from another
application, such as Microsoft Access.
Report Designer Design View
By default, when you create a Report Server project, Report Designer opens in Design view and displays the design
surface. By default, the design surface displays the report body and the report background.
The shortcut menu on the background provides options to add a page header and page footer, and from the View
menu, display a ruler and the Grouping pane.
Use the zoom control to increase or decrease the magnification of the report.
To design a report, drag report items from the Toolbox to the design surface, and then configure their properties
and alter their arrangement on the report.
Report Designer Preview
Use Preview to run the report and view the rendered report in the report viewer. Preview caches report data
locally. You can also set configuration properties to run the report in debug view, using a browser.
When you preview a report, Report Designer connects to the report data sources, runs dataset queries, caches the
data on the local computer, processes the report to combine data and layout, and renders the report. You can view
the report in on the Preview tab or you can set up project properties to view the report in debug mode and view it
directly in a browser.
Previewing Parameterized Reports. When you preview a report, the report is processed automatically if
all report parameters have valid default values. If one or more report parameters do not have a valid default
value, you must choose a value for each unassigned parameter, and then, on the report toolbar, click View
Report.
Understanding the Local Data Cache When you preview a report, the report processor runs all the
queries for datasets in the report using the current parameter defaults, and saves the results as a local data
cache (.rdl.data) file. You can continue to design your report without incurring the overhead of retrieving
this data again if you make no changes to either the report dataset queries or the report parameters.
Previewing the Report using Configuration Manager and Debug. In SQL Server Data Tools (SSDT),
project properties define how you want to deploy and debug your reports. These properties apply to all
reports and shared data sources in the project. To set the project properties, from the Project menu, click
Properties. Use these settings to test your reports and publish them to the report server.
Monitoring the Output Pane for Error Messages. When you preview a report and the report processor
detects a problem, it writes error messages to the Output pane.
Report Designer Menus
When a Report Designer project is active in SQL Server Data Tools (SSDT), the following toolbars are added to the
main toolbar. The Report Designer menus are visible only when in Design view.
Format Menu
When you select an item on the design surface, the Format menu contains the following options:
Foreground Color Select a text color. Black is the default text color.
Background Color Select a background color for your text boxes and data regions.
Font Specify whether the text is bold, italic, or underlined.
Justify Specify whether the text is right-aligned, centered, or left-aligned.
Align Specify how the selected objects are aligned in relation to one another within the report.
Make Same Size Adjust the size of the selected objects within the report.
Horizontal Spacing Adjust the horizontal spacing between the selected objects within the report.
Vertical Spacing Adjust the vertical spacing between the selected objects within the report.
Center in Form Center the selected object vertically and horizontally in relation to the Report Designer
window.
Order Move selected objects into the background or foreground.
Report Menu
When the report design surface has focus, the Report menu contains the following options:
Report Properties Select to open the Report Properties dialog box. In this dialog box, you can assign
general report properties, such as author name and grid spacing, and specify properties for the report
layout, such as the number of columns and page size. You can also include custom code, references to
assemblies and classes, and the names of data output elements, data transforms, and data schemas.
View Switch between the two Report Designer tabs: Design and Preview.
Page Header Add or delete a page header to the report. When you delete a page header, all items in the
page header are deleted.
Page Footer Add or delete a page footer to the report. When you delete a page footer, all items in the page
footer are deleted.
Grouping Pane Show or hide the Grouping pane.
View Menu
Use the View menu to display Report Designer windows and toolbars
Error List Use this option to display errors detected when publishing or previewing a report.
Output Use this option to display errors detected when publishing or processing a report, or for more
information about expression errors when a report displays the text "#Error".
Properties Window Use this option to display the property values for the currently selected report item on
the design surface. To see properties for nested report items, you must click a report item multiple times to
cycle through the hierarchy for a report item and its nested members. Check the name of the item that
appears at the top of the Properties pane to see which report item's properties are displayed.
Toolbox Use this option to display the Toolbox.
Other Windows Use this option to display the following pane:
Document Outline Use this option to display a hierarchical view of report items and their collections of
text boxes in a report.
Toolbars Use this option to display toolbars that support Report Designer features, including Report
Borders and Report Formatting. For more information, see Report Designer Toolbars.
Report Data Use this option to display the Report Data pane, where you can add report parameters, data
sources, datasets, images.
Project Menu
Use the Project menu to manage shared data sources and reports in a project. When you add or remove items
from the project, the hierarchical display of project items in Solution Explorer is automatically updated.
Add New Item Add a new shared data source or new report to the project.
Add Existing Item Add an existing shared data source or an existing report to the project.
Import Reports Import reports from another application, for example, Microsoft Access.
Exclude from Project Exclude items from the project. This option does not delete the item from your file
system.
Show All Files Show all files in a project.
Refresh Project Toolbox Items Refresh the toolbox cache when you install new custom report items in
your project.
Properties Open the Property Pages dialog box for this project. For more information, see Project
Property Pages Dialog Box.
Report Designer Toolbars
Report Designer provides the following specialized toolbars to use when designing reports:
Report Add a page header or page footer, set report properties, toggle the ruler or Grouping pane, or use
zoom to change your view of the report.
Report Borders Set the color, style, and width for all selected lines and the borders of all selected report
items.
Report Formatting Set the format of selected report items. For text boxes, the following types of
formatting can be changed using the toolbar: font properties and text color, background color, and text
justification.
Layout Set the drawing order of report items and merging cells within a data region.
Standard Open or save projects, display windows, and select the Debug configuration.
Use the View menu to control whether to display these toolbars. Other Visual Studio toolbars may be
disabled if their functionality does not apply to Report Designer features.
Source Control
SQL Server Data Tools can integrate with source plug-ins. Use the Projects and Solutions pages in the Options
dialog box to specify the plug-in and configure properties.
Custom Report Templates
To use custom reports as templates for new reports, you simply copy them to the ReportProject folder on the
computer on which SQL Server Data Tools is installed. By default, this folder is in the following location:
<drive>:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Private Assemblies\ProjectItems\ReportProject
.
When you add a new item to the report project, your custom report appears in the Templates pane.
You can also add custom styles to the report wizard.
Command Line Support for SQL Server Data Tools
SQL Server Data Tools is based on Microsoft Visual Studio and the underlying devenv.exe application. Before you
can use these options, you must set valid values for following two items:
Project properties for OverwriteDataSources, TargetDataSourceFolder, TargetReportFolder, and
TargetServerURL.
At least one set of configuration properties, for example, Debug or Release.
For more information, see Publishing Data Sources and Reports.
For a report server project, you can specify the following options from the command line:
/deploy Deploy reports by using the project properties specified in a configuration file. For example, the
following command deploys the reports specified by the solution file Reports.sln by using the Release
configuration settings that are specified in the project properties:
devenv.exe "C:\Users\MyUser\Documents\Visual Studio 2015\Projects\Reports\Reports.sln" /deploy
"Release"
/build Build the solution file, but do not deploy it. For example, the following command builds the reports
specified by the solution file Reports.sln by using the Debug configuration settings that are specified in the
project properties:
devenv.exe "C:\Users\MyUser\Documents\Visual Studio 2015\Projects\Reports\Reports.sln" /build "Debug"
/out Redirect the output generated by building a solution to the specified file. For example, the following
command redirects the output from the build in the previous example to a file named mybuildlog.txt.
devenv.exe "C:\Users\MyUser\Documents\Visual Studio 2015\Projects\Reports\Reports.sln" /build "Debug"
/out mybuildlog.txt
Keyboard Shortcuts in Reporting Services
Use keyboard shortcuts to:
Control windows and modes in SQL Server Data Tools:
DESCRIPTION
KEY COMBINATION
Build the selected project
CTRL+SHIFT+B
Display Properties window
F4
Display Data window
CTRL+Alt+D
Start debugging
F5
Move from one open window to the next
F6
Control items on the report design surface:
DESCRIPTION
KEY COMBINATION
Move focus from one report item to the next report item
TAB
Move selected report item
Arrow keys
Nudge selected report item
CTRL+Arrow keys
Increase or decrease the size of the selected report item
CTRL+SHIFT+Arrow keys
In a text box, move cursor to the beginning of the display
text that is visible
CTRL+HOME
In a text box, move cursor to the end of the display text
that is visible
CTRL+END
In a text box, select text from the current cursor position
to the beginning of the display text that is visible
SHIFT+HOME
In a text box, select text from the current cursor position
to the end of the display text that is visible
SHIFT+END
In a text box, select text from the current cursor position
to the beginning of the expression
CTRL+SHIFT+HOME
In a text box, select text from the current cursor position
to the end of the expression
CTRL+SHIFT+END
Open the shortcut menu for the selected report item
SHIFT+F10+Property Key on newer keyboards
Next steps
Download SQL Server Data Tools Solution Explorer
Reporting Services Reports
Report Definition Language
Deployment and Version Support in SQL Server Data Tools
More questions? Try asking the Reporting Services forum
Design Reporting Services Paginated Reports with
Report Designer (SSRS)
5/30/2017 • 13 min to read • Edit Online
Use Report Designer to create full-featured Reporting Services paginated reports and reporting solutions. Report
Designer provides a graphical interface in which you can define data sources, datasets and queries, report layout
positions for data regions and fields, and interactive features such as parameters and sets of reports that work
together.
Report Designer is a feature of SQL Server Data Tools (SSDT), a Microsoft Visual Studio environment for creating
business intelligence solutions. SQL Server Data Tools (SSDT) is not included with SQL Server. Download SQL
Server Data Tools.
Benefits of Report Projects
Report projects act as containers for report definitions and resources. Use projects to:
Organize reports and related items in one container.
Test report solutions that include reports and related items locally.
Deploy related items together. Use project properties and configuration management to deploy to multiple
environments.
Preserve a set of master copies for reports and related items. After deployment, published reports can be
accidentally modified.
Use the information in this topic to design paginated reports and related items for a single reporting project
in a SQL Server Data Tools (SSDT) solution. For more information about solutions and multiple projects in
SQL Server Data Tools, see Reporting Services in SQL Server Data Tools.
Shared Data Sources
Use SQL Server Data Tools to define and deploy shared data sources for a reporting solution. Shared data sources
can be deployed independently from other items in a project by using the OverwriteDataSources and
TargetDataSourceFolder properties. For more information, see Set Deployment Properties (Reporting Services).
In Report Designer, you work in both the Report Data pane and in Solution Explorer to define the data sources
used in a report. For more information, see Report Data Pane. You cannot use SQL Server Data Tools to open data
sources that are published to a report server or SharePoint site, but not included in the SQL Server Data Tools
solution. For that feature, use Report Builder authoring environment (SSRS).
SQL Server Data Tools is a client tool. You can test your reporting solution locally on your computer, deploy it to a
test environment for testing the server solution, and then deploy it to a production environment. After deployment,
verify that the data source processing extensions and data source credentials are configured for the report server
environment. You can use Configuration Manager to help manage the properties for different deployments. For
more information, see Reporting Services in SQL Server Data Tools (SSDT).
For more information, see Data Connections, Data Sources, and Connection Strings (Report Builder and SSRS).
Shared Datasets
Use SQL Server Data Tools to define and deploy shared datasets for a reporting solution. Shared datasets can be
deployed independently from other items in a project by using the OverwriteDatasets and TargetDatasetFolder
properties. For more information, see Set Deployment Properties (Reporting Services).
In Report Designer, you work in both the Report Data pane and in Solution Explorer to define shared datasets used
in a report. For more information, see Report Data Pane. You cannot use SQL Server Data Tools to open published
datasets directly from a report server or SharePoint site. For that feature, use Report Builder authoring
environment (SSRS) in Shared Dataset mode.
SQL Server Data Tools is a client tool. You can use query designers to help create and test your query results
locally in Preview. After deployment, you can manage shared datasets independently from the shared data sources
and reports that they depend on. For more information, see Report Embedded Datasets and Shared Datasets
(Report Builder and SSRS), Query Design Tools (SSRS), and Manage Shared Datasets.
Paginated Reports
Paginated reports are files that are stored in a report project. Reports can be used as stand-alone reports,
subreports, or the targets for drillthrough actions from main reports. Reports can be deployed independently from
other items in a project by using TargetReportFolder and other properties. For more information, see Set
Deployment Properties (Reporting Services).
NOTE
If you are publishing to a report server in SharePoint mode, some report solution features cannot be tested in the Report
Designer project. References to reports, subreports, and drillthrough reports must use fully-qualified URLs that can be tested
only after you deploy the report project. For more information, see URL Examples for Published Report Items on a Report
Server in SharePoint Mode (SSRS).
You can add reports to a project in the following ways:
Add a new report project. By default, a blank report opens in Report Designer. For more information, see
Add a New or Existing Report to a Report Project (SSRS).
Add a Report Wizard project. You create a report in a guided step-by-step manner. The Report Wizard
simplifies data definition and report design into a series of steps that give you a finished report. You can add
styles to customize the wizard for your own organization. For more information, see Add a New or Existing
Report to a Report Project (SSRS).
Add a new item of type Report. A blank report opens in Report Designer.
Add an existing item. An existing report definition (.rdl) opens in Report Designer. Opening a report or
project from an earlier version of Reporting Services might automatically upgrade the project to the current
version and the report to the current schema. For more information, see Upgrade Reports.
Import a Microsoft Access report. Import all reports from an Access database (.mdb, .accdb) or project
(.adp) file. Report Designer converts each report in a database or project file to RDL and saves it in the
report project. Not all of the functionality of an Access report transfers to a report definition (.rdl) file. For
more information, see Import Reports from Microsoft Access (Reporting Services) and Supported Access
Report Features (SSRS).
NOTE
You must have Access 2002 or a later version installed on the same computer that Report Designer is installed on in
order to use the import feature. The data source for the Access reports must be available when the reports are
imported.
Work directly in RDL. When you write a report in Report Designer, the report is saved in XML format as a
Report Definition Language (RDL) file. You can edit this file in Report Designer, a text editor, or any tool in
which you can edit XML.
When you edit the report definition source in Report Designer, you are working in the current RDL schema
for the version of SQL Server from which you installed the development tools. When you build a project, the
schema version might change depending on your deployment properties. For more information, see
Deployment and Version Support in SQL Server Data Tools (SSRS).
Editing RDL directly can result in a report that cannot be published to the report server or cannot run. As
with any XML file, ensure that XML-specific characters used within elements are properly encoded. When
you publish the report, the report server uses the schema to validate the XML contained within the RDL file.
To include elements that are not part of the RDL schema, place them in the Custom Element. The Custom
element can be read by custom rendering extensions, but is ignored by the rendering extensions provided
with Reporting Services. For example, you can use the Custom element to store comments in the report.
For more information, see Report Definition Language (SSRS).
Report Parts
In Report Designer, after you create tables, charts, and other paginated report items in a project, you can publish
them as report parts to a report server or SharePoint site integrated with a report server so that you and others
can reuse them in other reports. For more information, see Report Parts in Report Designer (SSRS).
Report parts can be deployed independently from other items in a project by using TargetReportPartFolder and
other properties. For more information, see Set Deployment Properties (Reporting Services).
Resources
You can add files to your project that are related to your report but not processed by the report server. For
example, you can add images for pictures or ESRI shapefiles for spatial data. For more information, see Resources.
Paginated Report Layout
To create the report layout, drag report items and data regions from the Toolbox to the design surface and arrange
them. Drag dataset fields to the items on the design surface to add data to the report. To organize data in groups in
a tablix data region, drag dataset fields to the Grouping pane. Because report authoring tools are essentially a way
to create report definitions, the approach to report design is quite similar between Report Builder and Report
Designer.
Preview a Paginated Report
Use Preview to verify the report data and layout design. When you preview a report, the report processor
validates the report definition schema and expression syntax and lists issues in the Output window.
NOTE
When you preview a report, the data for the report is cached to a file on the local computer. When you preview the same
report again using the same query, parameters, and credentials, Report Designer retrieves the cached copy rather than
rerunning the query. The data file is saved as <reportname>.rdl.data in the same directory as the report definition file. The
file is not deleted when you close Report Designer.
You can preview a report in the following ways:
Preview view. Click the Preview tab. The report runs locally, using the same report processing and
rendering functionality that is provided with the report server. The report that is displayed is an interactive
image; you can select parameters, click links, view the document map, and expand and collapse hidden
areas of the report. You can also export the report to any of the installed rendering formats.
Standalone Preview. Run the local report in a browser. By using a debug configuration, you can also use
this mode to debug custom assemblies that you write. There are three ways to run a project in Debug mode:
On the Debug menu, click Start Debugging.
On the Visual Studio standard toolbar, click the Start button.
Press F5.
If you use a project configuration that builds the report but does not deploy it, the report that is
specified in the StartItem property of the current configuration opens in a separate preview window.
NOTE
To use Debug mode, you must set a start item. In Solution Explorer, right-click the report project, click Properties,
and in StartItem, select the name of the report to display.
If you wish to preview a particular report that is not the start item for the project, select a configuration that
builds the report but does not deploy it (for example, the DebugLocal configuration), right-click the report,
and then click Run. You must choose a configuration that does not deploy the report; otherwise, the report
will be published to the report server instead of displayed locally in a preview window.
Print Preview.
When you first view a report on in Preview mode or in the preview window, the view of the report
resembles a report produced by the HTML rendering extension. The preview is not HTML, but the layout and
pagination of the report is similar to HTML output.
You can change the view to represent a printed report by switching to print preview mode. Click the Print
Preview button on the preview toolbar. The report will display as though it were on a physical page. This
view resembles the output produced by the Image and PDF rendering extensions. Print preview is not an
image or PDF file, but the layout and pagination of the report is similar the output in those formats. You can
choose the size of the report image, for example, set the width of the page.
Print preview helps you identify many of rendering problems you might encounter were you to print the
report. Common rendering problems include:
Extra blank pages because the report is too wide to fit on the paper size you specified for the report.
Extra blank pages because the report contains a matrix that dynamically expands to exceed the width
of the paper specified.
Page breaks between groups do not work the way you want.
Headers and footers do not display as expected.
Report layout needs modification to read better in a printed format.
Save and Deploy Paginated Reports
In Report Designer, you can save reports and other project files locally, or deploy them to a report server or
SharePoint site. Shared data sources, shared datasets, reports, report resources, and report parts can be deployed
independently or together depending on project deployment properties that you configure. For more information,
see Configuration and Deployment Properties.
In Report Designer, it is important to understand that you design a report using the report definition schema that is
supported by the current version of Reporting Services in SQL Server Data Tools (SSDT). When you set project
deployment properties for a specific report server or SharePoint site, and then save the report, Report Designer
saves the report definition to the build directory in the schema that matches the version on the target report
server. To create reports that can be published on a down-level report server, Report Designer drops report items
that do not exist in the target schema. This occurs automatically and without prompting. When this happens, the
original report definition is preserved in the project folder. The modified report definition that is deployed is in the
build folder.
NOTE
For debugging expressions and deployment errors, you must view the report definition in the build folder. Do not use View
Source. View Source displays the report definition source from the project folder.
For more information, see Deployment and Version Support in SQL Server Data Tools (SSRS).
Save a Report Locally
When you work on report or other project items in Report Designer, the files are saved to your local computer or a
share on another computer that you have access to.
If you are using source control software, you might be checking your reports into the source control server when
you save the report. For more information, see Source Control.
Deploy or Publish Paginated Reports
From SQL Server Data Tools, you can deploy reports or other project items to multiple versions of Reporting
Services report servers. Use project configurations to control the upgrade of report definitions to schema versions
compatible with target report servers. The properties controlled by project configurations include the target report
server, the folder where the build process temporarily stores report definitions for preview and deployment, and
error levels. For more information, see Configuration and Deployment Properties and Set Deployment Properties
(Reporting Services).
Export a Paginated Report to a Different File Format
Reports can be exported to a variety of formats and these formats affect how some report layout and interactivity
features function. For more information about design considerations for various output formats, see Export
Reports (Report Builder and SSRS).
Report Validation and Error Levels
Reports are validated before preview and during deployment. A number of build issues can occur when reports are
built. Reports might contain strings such as expressions or queries that are incompatible with the version of
Reporting Services that the project configuration specifies, for example.
Use the ErrorLevel property to manage the build warnings and errors. The ErrorLevel property can contain a value
from 0 to 4 inclusive. The value determines which build issues are reported as errors and which are reported as
warnings. The default value is 2. The warnings and errors are written to the SQL Server Data Tools (SSDT)Output
window.
Issues with severity levels less than or equal to the value of ErrorLevel are reported as errors; otherwise, they are
reported as warnings.
The following table lists the error levels.
ERROR LEVEL
DESCRIPTION
0
Most severe and unavoidable build issues that prevent
preview and deployment of reports.
1
Severe build issues that change the report layout drastically.
2
Less severe build issues that change report layout in
significantly.
3
Minor build issues that change the report layout in minor
ways that might not be noticeable.
4
Used only for publishing warnings.
When you attempt to preview or deploy a report that contains report items new in SQL Server 2016 Reporting
Services (SSRS), those report items can be removed from the report. By default, the ErrorLevel property of the
configuration is set to 2, which would cause the build of the report to fail when the map is removed. However, if
you change the value of the ErrorLevel property to 0 or 1, the map is dropped, a warning issued, and the build
process continues.
Next steps
Download SQL Server Data Tools
Reporting Services in SQL Server Data Tools
Query Design Tools
Deployment and Version Support in SQL Server Data Tools
More questions? Try asking the Reporting Services forum
Add a New or Existing Report to a Report Project
(SSRS)
3/24/2017 • 2 min to read • Edit Online
In SQL Server Data Tools (SSDT), you can add a new Reporting Services paginated report by using the Report
Wizard or by adding a new blank report to your project. You can also add an existing report. After you add a
report, you can see the report name listed under the Reports folder in your project.
NOTE
To preview a report with existing data sources, you must have permissions to the data source from your report authoring
client. For more information, see Data Connections, Data Sources, and Connection Strings.
After you add a report, you can define data sources, datasets, and design a report layout. To get started, see Create
a Basic Table Report (SSRS Tutorial) or Tables (Report Builder and SSRS).
To add a new report using the Report Wizard
1. In Solution Explorer, right-click the Reports folder, and then click Add New Report. The Report Wizard
dialog box opens.
The wizard steps you through creating a data source, creating a dataset with a query, defining groups,
specifying a layout and creating the report. The steps include:
Select a Data Source. The first step in creating a report is to define a data source. Report Wizard
provides a list of all shared data sources in the report project, in addition to an option to create a new
data source.
Design a Query. The next step is to design a query. You can type the query string, build it using
Query Designer, or import a query from another report. For information about Query Designers, see
Reporting Services Query Designers.
Choose a Report Type. The next step is to select the type of report you want. You can choose a
tabular or matrix report. A tabular report has a fixed number of columns. A matrix, or crosstab, report
has a variable number of columns based on the results of the query. A map report displays analytical
against a geographic background.
Name the Report. The final step is to name the report and verify the fields that will be included in
the report. When all steps are completed, Report Designer creates the report and adds it to the report
server project.
To add a new blank report
1. From the Project menu, click Add New Item.
2. In Templates, click Report.
3. Click Add.
A new blank report is added to the project and displayed on the design surface.
To add an existing report
1. From the Project menu, click Add, and then Existing Item.
2. Navigate to the location of the .rdl file, select it, and then click Add.
The report is added to the project under the Reports folder. When you close and re-open the project,
reports are sorted alphabetically.
See Also
Reporting Services Tutorials (SSRS)
More questions? Try the Reporting Services forum
Deployment and Version Support in SQL Server
Data Tools (SSRS)
3/24/2017 • 3 min to read • Edit Online
SQL Server Data Tools supports the following scenarios:
Open report definitions (.rdl) and report server projects (\.rptproj).
Build report definitions.
Preview reports in Report Designer.
Deploy reports to report servers.
Configuration and Deployment Properties
SQL Server Data Tools (SSDT) supports project configurations. A project configuration consists of a set of
properties that specify locations and behaviors when a project is built either as a step in previewing or deploying
reports. To learn more about project configurations, see the Visual Studio documentation.
Use project configurations to control the upgrade of report definitions to schema versions compatible with target
report servers. The properties controlled by project configurations include the target report server, the folder
where the build process temporarily stores report definitions for preview and deployment, and error levels.
Reports are built before they are rendered as previews in Report Designer or deployed to the report server.
You set the configuration properties in the SQL Server Data Tools (SSDT) Project Property dialog box.
The build and deployment properties include:
OutputPath is a build property that identifies the path of folders to store the report definition used in build
verification, deployment, and preview of reports.
ErrorLevel is a build property that identifies the severity of the build issues that are reported as errors.
Issues with severity levels less than or equal to the value of ErrorLevel are reported as errors; otherwise, the
issues are reported as warnings. For more information, see The “Report Validation and Error Levels” section
in Design Reports with Report Designer (SSRS).
TargetServerVersion is a deployment property that identifies the expected version of SQL Server Reporting
Services that is installed on the target report server specified in the TargetServerURL property.
When you specify the earlier version of SQL Server Reporting Services in the Project Property dialog box,
the reports are not reverted automatically to the earlier version. As such, a Report Server project can
contain reports from the two different versions of SQL Server. When the Report Server project is deployed,
all reports in the project are converted to the version specified in TargetServerVersion.
You can add more than one project configuration to a project; each one is used for a different scenario,
such as deploying to different versions of report servers. For more information, see Set Deployment
Properties (Reporting Services) and Project Property Pages Dialog Box.
Supported Versions
NOTE
SQL Server Data Tools (SSDT), the 32-bit development environment for Report Server projects, is not designed to run on
Itanium-based computers and is not installed on Itanium-based servers. However, support for SQL Server Data Tools is
available for x64-based computers.
The following table describes the supported versions for authoring and publishing reports in SQL Server Data
Tools (SSDT).
NOTE
The schema has not changed since SQL Server 2008.
PROJECT OR FILE TYPE
VERSION
AUTHOR REPORTS
PUBLISH REPORTS
Report Server Project
SQL Server 2016
Reporting Services
(SSRS)
2016 RDL schema
SQL Server 2016
Reporting Services
(SSRS)
SQL Server 2014
2014 RDL schema
SQL Server 2014
Reporting Services
SQL Server 2012
2012 RDL schema
SQL Server 2012
Reporting Services
SQL Server 2008 R2
2008 R2 RDL schema
SQL Server 2008 R2
Reporting Services
SQL Server 2008
2008 RDL schema
SQL Server 2008
Reporting Services
report server only
or
NOTES
Report Server Wizard
Project
Report Server Project
or
Report Server Wizard
Project
Report Server Project
or
Report Server Wizard
Project
Report Server Project
or
Report Server Wizard
Project
Report Server Project
or
Upgrades 2003 RDL
and 2005 RDL to the
2008 RDL schema
locally.
Report Server Wizard
Project
For more information about opening reports in a previous version of the report definition schema, see Upgrade
Reports. For more information about specific report definition schemas, see Report Definition Language
Specification.
See Also
Publishing Data Sources and Reports
URL Examples for Items on a Report Server SharePoint Mode
4/14/2017 • 10 min to read • Edit Online
To publish reports and related items to a SharePoint library, you can either publish the content using the Reporting
Services authoring tools such as Report Designer or you can upload the content by using SharePoint site actions.
SharePoint sites use different Web addresses than a Reporting Services report server in native mode. A SharePoint site
Web hierarchy includes the SharePoint Web application, a top-level site, optional subsites, and libraries. You must know
how to create a URL address that specifies the SharePoint server as well as the location in the SharePoint site hierarchy
where you want to publish a report or related items.
Items related to a report include shared data sources, subreports, drillthrough reports, and resources such as Webbased image files. A report that has been published to a SharePoint library must specify these related items by their
location in the SharePoint library.
Use the examples in this topic to help create URLs to reports and related items in your reporting solutions.
Site Hierarchy
When you configure a report server to run in SharePoint integrated mode, the SharePoint Web hierarchy is used to
address items that are processed and managed on a report server.
The following elements of the Web hierarchy can be used to access and secure report server content. Other objects
such as lists and pages are not used to access report server content and therefore are not described in the following
table.
OBJECT
DESCRIPTION
SharePoint Web application
A SharePoint Web application can be installed as a stand-alone
server or under a farm that contains a collection of virtual
servers. A Web application has a URL (for example,
http:*//servername* ) and can contain multiple sites.
Site
A site is either a parent site for a Web application or a subsite.
SharePoint library
A library contains documents or folders. A library or folder in a
library is the only site object that can store reports, report
models, shared data sources, and external images.
Item
Report server items that you can reference in a URL include a
report definition for a report or subreport, a report model, a
shared data source, or an external image.
URL Syntax and Rules
Each report server item in a library is identified by a fully qualified URL that includes a protocol prefix, server name, site,
library, file name, and file name extension for the file type.
URL for a SharePoint Server
You must use a URL to the SharePoint server when you deploy a Report Server or Report Model project from SQL
Server Data Tools (SSDT) to the report server.
To find the name of the server to use, open a browser and locate the SharePoint library where you want to publish a
report. The server name appears immediately after the protocol prefix, for example,
http:*//servername*
.
Using the Reporting Services URL proxy endpoint is not supported. A proxy endpoint includes a port number, for
example, http:*//servername:8080/reportserver* .
URL for a SharePoint Server Site or Subsite
When you deploy a report or report data source, you must use a URL to a SharePoint site and subsite, if there is one. In
the URL, the site name appears immediately after the server name., for example, http://*servername/site* or
http://*servername/site/subsite* .
On a Microsoft Office SharePoint Server 2007 or SharePoint Server 2010 Web application, the site and subsite
frequently correspond to the tabs on the main site. To find the site name or subsite name, click Home, and then All Site
Content. Scroll to the bottom and look for Sites and Workspaces. The list of sites appears in this section.
URL for a SharePoint Library
When you deploy a report or related item to a SharePoint library, you must use a URL to the SharePoint library. The
URL to use for a library differs depending on the version of SharePoint you are using.
On Microsoft Windows SharePoint Services 3.0 or SharePoint Foundation 2010, the library appears after the server
name, for example, http://*servername/*Shared Documents .
On Office SharePoint Server 2007 or SharePoint Server 2010, the library appears after the site and subsite. For
example, http://*servername/site/*Documents .
To find the path information for a new SharePoint library or for an unfamiliar site, open a browser and locate the
SharePoint library where you want to publish your reports. If the library is empty, upload any file. Right-click the file
and select Properties to open the Properties window. The address of the file contains the URL values that you need for
a publish operation.
Fully qualified URLs for Items on a SharePoint Site
Items that are stored in a SharePoint library are always addressed through a fully qualified URL that starts with the Web
application ( http://*server* ) as the root node, and concludes with the name of the file that you are referencing.
File names in the URL must include a file name extension.
You cannot use relative URLs for dependent items in reports that you publish to a SharePoint site. For example, you
cannot use a relative URL to reference a shared data source, report model, or subreport. You must always specify the
fully qualified URL to a SharePoint library for each item. There is no way to predict where a dependent file might be
located as there is no predefined hierarchy to the sites that you can use to parse a URL format.
When you publish or upload a report that contains dependent items, you must set the references to the dependent
items after the report is published. References that worked correctly in Preview mode in Report Designer are not
guaranteed to work after the report is published. For more information, see Publishing from an Authoring Tool to a
SharePoint Library in this topic.
URLs for External Images
A report definition can include an image file that is stored as an external file. You can reference that file in the report
definition by setting a fully qualified URL to the image file. It can be stored on a SharePoint site or on a remote
computer.
IMPORTANT
If the external URL is for an image on a SharePoint site, the broken image icon will appear when you preview the report in Report
Builder. When you upload the report to the SharePoint site, and render the report in connected mode, the broken image icon will
appear if you have only View Items permissions.
Regardless of the report server mode, references to an external image file in a report must be a fully qualified URL. Also,
referencing an external image file typically requires that you configure the unattended report processing account.
Specifying Subreports and Drillthrough Reports
Subreports must reside in the same folder as the main report. You cannot specify a relative folder.
To specify drillthrough reports, include the URL in an expression. For example, to specify the report that is named
SalesDetails as a drillthrough report, in the Action for the text box or placeholder text, set ReportName to the following
expression:
="http://site/subsite/documentlibrary/SalesDetails.rdl"
Reserved Names on SharePoint Sites
If you are creating or constructing a URL to an item that is located on a SharePoint site, know that the words Personal
and Sites are both reserved names under the default site.
Examples of URLs
When publishing items to a SharePoint library, you must specify fully qualified URLs to the target library. A fully
qualified SharePoint URL includes the SharePoint Web application, site, library, folder (optional), file, and file name
extension. The following examples provide several illustrations of the syntax you should use.
TARGET
EXAMPLE URL
A SharePoint server.
http://TestServer
A SharePoint server site or subsite.
http://TestServer/toplevelsite/subsite
The Company Sales sample report in Shared Documents on a
Windows SharePoint Services or SharePoint Foundation 2010
deployment.
http://TestServer/TestSite/Shared%20Documents/Company%20Sales.rdl
The Company Sales sample report in Documents/Doc folder on
a Office SharePoint Server or SharePoint Server 2010 instance.
http://TestServer/TestSite/Documents/Doc/Company%20Sales.rdl
The Company Sales sample report in Report Center on an
Office SharePoint Server or SharePoint Server 2010 instance.
http://TestServer/TestSite/Reports/Doc/Company%20Sales.rdl
Publishing from an Authoring Tool to a SharePoint Library
When you use a report authoring tool to publish reports and related files to a library, the files are validated before they
are added. If you upload reports and related files by using the Upload action on a SharePoint library, no validation
check occurs. You will not know whether the file is valid until you access the report by managing, editing, or running it.
NOTE
In order to publish reports to a SharePoint site from SQL Server Data Tools (SSDT), you might need to add the SharePoint site to
your list of trusted locations in the Internet Explorer browser.
Shared Data Sources
When you publish a shared data source from a report authoring tool, you set the project property
TargetDataSourceFolder. The target data source folder must be a URL to a SharePoint library. Unlike in Reporting
Services native mode, you cannot specify a relative folder; relative paths are not valid. If a folder in the Document
Library path does not exist, one will be created.
When you publish a shared data source (.rds) file to a SharePoint site, this changes the data source file to an .rsds file
name extension. The .rsds file cannot be saved locally from a SharePoint site and imported into an existing Reporting
Services project. Shared data sources with file name extensions .rds and .rsds are not interchangeable.
Shared Data Sources from Report Designer
If you are publishing shared data sources from a Report Designer project, you can either use a URL that specifies the
target library or you can leave the property blank. Unlike in Reporting Services native mode, you cannot specify a
relative folder; relative paths are not valid. If a folder in the Document Library path does not exist, one will be created. If
you leave the target data source folder blank, the data source will be published in the target report folder.
File Names
File names in a URL for report items must include a file name extension. The file name extension determines the file
type. When you publish report items from a report authoring tool, the file name extension is included automatically. If
you upload a report item to a SharePoint library, you must include a file name extension.
If you do not specify a file name extension for items that you upload to a SharePoint site, the
rsInvalidDataSourceReference error will occur. File names may not include characters that are not recognized as
valid file name characters by SharePoint applications. Do not include the following characters: # % & * : < > ? / { | }.
Differences Between Uploading and Publishing
When you use Report Designer or Report Builder to publish reports and related files to a library, the files are validated
before they are added. If you upload reports and related files by using the Upload action on a SharePoint library, no
validation check occurs. You will not know whether the file is valid until you access the report by managing, editing, or
running it.
Updating a Published Item
After you have published or uploaded an item to a SharePoint library, you should check the item out of the library
before updating it. While the report is checked out to you, you will be the only user who has permission to change the
report. When you are finished, check it back in.
If you upload or publish a report without checking the document out first (for example, by uploading an item that has
the same name as an existing item), the report server will check it out for you, add the updated report as a new version
of the existing item, and then check the document back in.
External Images as Resources
A report server that runs in native mode supports the concept of a resource, which is defined as any file that is stored
and secured on the report server, but is not processed by the report server. In native mode, it can be any kind of file.
When a report server runs in SharePoint integrated mode, the concept of a resource has a narrower definition. The
report server retains the concept of a resource for storing reports that reference an external image. This applies if the
report is a snapshot or a copy that is kept for internal use.
See Also
Publish a Report to a SharePoint Library
Publish a Shared Data Source to a SharePoint Library
Project Property Pages Dialog Box
Set Deployment Properties (Reporting Services)
3/24/2017 • 5 min to read • Edit Online
In SQL Server Data Tools (SSDT), you must specify the report server and optionally the folders for reports and
shared data sources so that you can publish the items in a Report Server project to a report server. The properties
and values that SQL Server Data Tools (SSDT) needs to build, preview an deploy reports are stored in project
configurations of the Report Server project. You can create multiple named sets for these project properties, so
that you can conveniently switch between property sets. Each set of properties is a configuration. For example,
you can have a configuration for publishing reports to a test server and a different configuration for publishing
reports to a production server.
Use Configuration Manager to create and manage sets of project properties in project configurations.
Configuration Manager is a feature supported by Visual Studio, on which SQL Server Data Tools is based.
NOTE
Do not confuse this feature with the Reporting Services Configuration Manager, which is used to configure Reporting
Services after installation. For more information, see Configure and Administer a Report Server (SSRS Native Mode).
NOTE
In SQL Server Data Tools, the action of publishing reports from a Report Server project or solution is known as deploying
reports.
To set deployment properties
1. Right-click the report project, and then click Properties.
2. In the Property Pages dialog box for the project, select a configuration to edit from the Configuration
list. Common configurations are DebugLocal, Debug, and Release.
NOTE
You can use multiple configurations to switch quickly between different report servers or settings.
3. In the OutputPath textbox, type or paste the path in your local file system to store the report definition
used in build verification, deployment, and preview of reports. The path must be different than the path
that you use for the project and a relative path that is a child folder under the path of the project.
4. In the ErrorLevel text box, type the severity of the build issues that are reported as errors. Issues occurring
when building reports, data sources, or other project resources with severity levels less than or equal to
the value of ErrorLevel are reported as errors; otherwise, the issues are reported as warnings. Any error
will cause the build task to fail. The valid severity levels are 0 through 4 inclusive. The default value is 2.
ErrorLevel can be used to increase or decrease the sensitivity of the build. For example, when a report
with a map is built during deployment to a SQL Server 2008 report server an error displays by default and
building the report fails. If you lower ErrorLevel the map is removed from the report, a warning displays,
and building the report continues.
5. In the StartItem list, select a report to display in the preview window or in a browser window when the
report project is run.
6. In the OverwriteDataSources list, select True to overwrite the shared data source on the server each time
shared data sources are published, or select False to keep the data source on the server.
7. In the TargetServerVersion list, select SQL Server 2016 version of Reporting Services or select Detect
Version to automatically determine the version installed on the server identified by the TargetServer URL
property. The default value is SQL Server 2016 or later.
Use TargetServerVersion to customize the built reports, placed in the path specified in OutputPath, for
the version of the report server specified in TargetServer URL.
8. In the TargetDataSourceFolder text box, type the folder on the report server in which to place the
published shared data sources. The default value for TargetDataSourceFolder is Data Sources. If you
leave this value blank, the data sources will be published to the location specified in TargetReportFolder.
9. In the TargetReportFolder text box, type the folder on the report server in which to place the published
reports. The default value for TargetReportFolder is the name of the report project.
NOTE
For a report server running in native mode, you must have Publish permissions on the target folder to publish
reports to that folder. Publish permissions are provided through a role assignment that maps your user account to
a role that includes publish operations. For more information, see Create and Manage Role Assignments. For a
report server running in SharePoint integrated mode, you must have Member or Owner permission on the
SharePoint site. For more information, see SharePoint Site and List Permission Reference for Report Server Items.
10. In the TargetServerURL text box, type the URL of the target report server. Before you publish a report, you
must set this property to a valid report server URL. When publishing to a report server running in native
mode, use the URL of the virtual directory of the report server (for example, http://server/reportserver or
https://server/reportserver). This is the virtual directory of the report server, not Report Manager.
When publishing to a report server running in SharePoint integrated mode, use a URL to a SharePoint toplevel site or subsite. If you do not specify a site, the default top-level site is used (for example,
http://servername, http://servername/site or http://servername/site/subsite).
To set Configuration Manager properties
1. Right-click the report project, and then click Properties.
2. In the Property Pages dialog box for the project, click Configuration Manager.
3. In the Configuration Manager dialog box, select the configuration to edit. The currently active
configuration is displayed as Active(<configuration>).
4. In Project Contexts, for each project in the solution, select or clear Build or Deploy.
NOTE
If Build is selected, Report Designer builds the report project and checks for errors before previewing or publishing
to a report server. If Deploy is selected, Report Designer publishes the reports to the report server as defined in
deployment properties. If Deploy is not selected, Report Designer displays the report specified in the StartItem
property in a local preview window.
See Also
Publishing Data Sources and Reports
Previewing Reports
Report Designer F1 Help
URL Examples for Published Report Items on a Report Server in SharePoint Mode (SSRS)
Project Property Pages Dialog Box
Publishing Reports to a Report Server
Dock the Report Data Pane in Report Designer
(SSRS)
3/24/2017 • 1 min to read • Edit Online
In Reporting Services Report Designer in SQL Server Data Tools (SSDT), the Report Data pane displays a
hierarchical view of data objects that you can use in a report, including data sources, datasets, fields, parameters,
and images. Data sources in this view can be embedded or references to shared data sources that are displayed in
Solution Explorer.
To display the Report Data pane
In Design view, on the View menu, select Report Data, or use CTRL+ALT+D.
To dock the Report Data pane
1. Grab the title bar of the Report Data pane and start to drag the pane. Docking arrows appear on the design
surface.
2. Drop the Report Data pane onto one of the arrows to dock the pane.
To change the Report Data pane from a docked window to a tabbed window
Right-click the title bar of the Report Data pane and then click Dock as Tabbed Document.
To change the Report Data pane from a tabbed window to a docked window
Right-click the Report Data tab and then click Dock.
To toggle between the last two display states, double-click the title bar of the Report Data pane.
See Also
Report Data Pane
Data Connections, Data Sources, and Connection Strings (Report Builder and SSRS)
Report Designer F1 Help
3/24/2017 • 1 min to read • Edit Online
This section provides F1 Help for the SQL Server Reporting Services Report Designer wizards, views, and dialog
boxes in SQL Server Data Tools (SSDT). Alternatively, you can open the F1 Help while working with the dialog box
by pressing F1 or by clicking the Help button displayed in the dialog box.
See Also
Install SQL Server Data Tools - Business Intelligence for Visual Studio
Feature Refernce (Reporting Services)
Reporting Services Reports (SSRS)
Document Outline
3/24/2017 • 1 min to read • Edit Online
Use the Document Outline window to view the hierarchy of report items in a report. Tablix data regions display all
the text boxes and other report items that are contained in Tablix cells. When you select a report item on the design
surface, the corresponding report item is selected in the Document Outline window. Use this view to locate report
items on the design surface. For example, when you preview a report with expression errors, the Output window
displays a message for each error. The message includes the name of the text box that contains the expression with
the error. You can click the name of the text box in the Document Outline window, see it selected on the design
surface, and view the expression that contained the error.
If the Document Outline window is not visible, on the View menu, click Other Windows, and then click Document
Outline. Or use CTRL+ALT+T.
Options
Expand All
Click to expand all nodes in the hierarchy.
Collapse All
Click to collapse all nodes in the hierarchy.
Design View
3/24/2017 • 2 min to read • Edit Online
In Reporting Services Report Designer, use Design view to arrange report items in the report. Design view is
sometimes called the design surface or layout view.
Report Design Surface
The design surface consists of three sections:
report body
page header
page footer
Use the Toolbox to select items to place in any of these three sections. Use the Report Data pane to view images,
parameters, data sources, and datasets, including dataset queries and field lists. After you add report items to the
design surface, drag dataset fields from the Report Data pane onto data regions such as table, matrix, or list. Each
item on the report design surface contains properties that can be managed using a properties dialog box or the
Properties pane.
Toolbox
The Toolbox lists data regions and other report items that are available for your report. To add report items from
the Toolbox, double-click the item or drag it to the design surface. You can then change the shape and size by using
the object handles.
Report Data Pane
To view the Report Data pane, on the View menu, click Report Data. Use this pane to define parameters, images,
data sources, and datasets, and to reference built-in fields such as ReportName. To add a new item, click the New
menu and select an item. To add calculated fields to an existing dataset, click Dataset, and in the Dataset
Properties dialog box, select Fields. Select an item and click Edit to open the Properties dialog box. You can also
right-click items in the Report Data pane to add items or update their properties.
Drag items from the Report Data pane to data regions and text boxes on the design surface to add data and images
to a report.
For more information, see Report Data Pane.
Grouping Pane
Groups are used to organize your report data into a visual hierarchy and to calculate totals. Use the Grouping pane
to view the groups defined for a table, matrix, or list data region. By default, the Grouping pane displays all the
groups for the selected data region as a flattened list. The Grouping pane is disabled for Chart and Gauge data
regions.
To see the groups in relationship to one another, toggle the Grouping pane to Advanced mode. This mode displays
the hierarchy of group members, a visual display of cells in the data region that correspond to each group.
For more information, see Grouping Pane.
Page Header and Page Footer
A page header and page footer run along the top and bottom of each page, respectively. Headers and footers can
contain static text, images, lines, rectangles, borders, background color, and background images. To add report
items to the header or footer, right-click the design surface and select Header or Footer. Header and footer sections
appear on the design surface.
Properties Pane
Use the Properties pane to view properties for the currently selected report item on the design surface or the
currently selected group in the Grouping pane. Alternatively, you can right-click on a selected report item or group
and then click Properties to open the corresponding Properties dialog box for the report item or group.
See Also
Page Headers and Footers (Report Builder and SSRS)
Report Design Tips (Report Builder and SSRS)
Preview View
3/24/2017 • 1 min to read • Edit Online
In Reporting Services Report Designer, use Preview view to display the rendered report. When a report is
previewed, Report Designer runs the report locally and displays it in the Preview view. In preview mode, the report
is processed in full. If the report has a complex query or has a large amount of data, preview might take several
minutes to complete the first time you view it. For subsequent changes that affect only the format of the report,
preview uses cached data.
Options
Use the toolbar to manage preview functions.
(1) First Page
Choose this option to go to the first page of the report.
(2) Previous Page
Choose this option to go to the previous page of the report.
(3) Current Page
Displays the current page of the report.
(4) Total Pages
Displays the total number of pages in the report.
(5) Next Page
Choose this option to go to the next page of the report.
(6) Last Page
Choose this option to go to the last page of the report.
(7) Back to Parent Report
Choose this option to go to the parent report. This option is used to navigate drillthrough reports.
(8) Stop Rendering
Choose this option to stop the rendering process.
(9) Refresh
Choose this option to refresh the data cache and run the report again.
(10) Print
Choose this option to print the report.
(11) Print Layout
Choose this option to toggle between the preview report and the view of the report as it will appear on the printed
page.
(12) Page Setup
Choose this option to conveniently change page and print properties. Use Print Layout to view changes before
printing.
(13) Export
Choose this option to export the rendered report in a specific format.
(14) Zoom
Select a zoom factor to zoom in or out on the report.
(15) Find Text in report
Type text to search for a match within the report. You cannot use search operators. Click Find to search for the first
instance.
(16) Show or Hide Parameter Area
Choose this option to show or hide the parameters boxes for reports with parameters.
(17) Find
Choose this option to begin searching the report for the search text.
(18) Find Next
Choose this option to search for the next instance of the search text.
See Also
Previewing Reports
Report Designer F1 Help
Grouping Pane
3/24/2017 • 4 min to read • Edit Online
When designing Reporting Services reports, the Grouping pane displays the row groups and column groups for
the currently selected Tablix data region. The Grouping pane is not available for the Chart or Gauge data regions.
The Grouping pane consists of a Row Groups pane and a Column Groups pane. The Grouping pane has two
modes: default and Advanced. Default mode displays a hierarchical view of the dynamic members for row and
column groups. Advanced mode displays both dynamic and static members for row and column groups. A group
is a named set of data from a report dataset that is displayed on a data region. Groups are organized into
hierarchies that include static and dynamic members. For more information, see Understanding Groups (Report
Builder and SSRS).
If you do not see the Grouping pane, on the Report menu, click Grouping.
Cells in the row and column group areas can be static or dynamic members of a group. Static members repeat
once per group and typically contain labels or totals. Dynamic members repeat once per group instance and
typically contain the unique values of the group expression. As you select Tablix cells in the row group area or
column group area, the corresponding group member is selected in the Row Groups or Column Groups pane.
Conversely, if you select groups in the Grouping pane, the corresponding cell associated with the group member is
selected on the design surface. For more information about Tablix row and column group areas, see Tablix Data
Region Areas (Report Builder and SSRS).
The Grouping pane supports the following modes:
Default. Use the default mode to add, edit, or delete groups. You can add parent, child, and detail groups by
dragging fields from the Report Data pane and inserting them in the group hierarchy. To add an adjacent
group, you must use the Add Group shortcut. For more information, see Add or Delete a Group in a Data
Region (Report Builder and SSRS).
Advanced. Use the Advanced mode to view all members of row and column groups, and to set properties
on static members. When you create groups or add totals, the properties that control how the Tablix data
region renders rows and columns on each report page are set automatically. To manually adjust these
properties, you must set them on the Tablix member. For more information, see Controlling the Tablix Data
Region Display on a Report Page (Report Builder and SSRS).
Default Mode
In default mode, the Row Groups pane and the Column Groups pane display a hierarchical view for all parent
groups, child groups, and adjacent groups. A child group appears indented under its parent group. An adjacent
group appears at the same indent level as its sibling groups. The following figure shows a Tablix data region with
nested row groups and nested and adjacent column groups.
The Grouping pane displays the corresponding row and column groups. In the following figure, the group based
on subcategory has been selected in the Row Groups pane, and the [Subcat] grouping cell is selected in the Tablix
data region:
In the Row Groups pane, the group based on subcategory is a child of the group based on category. In the Column
Groups pane, the country/region group is a child of the geography group. The year group and the country/region
groups are adjacent groups.
For more information, see Tablix Data Region Cells, Rows, and Columns (Report Builder) and SSRS.
Advanced Mode
In Advanced mode, you can view all static and dynamic members of a group. When you select a member, the
Properties window displays properties for the currently selected Tablix member.
To toggle Advanced mode, right-click the down arrow at the side of the Column Groups pane, and then click
Advanced Mode.
In most cases, properties that control the display of static and dynamic group rows and group columns are set
automatically when you create a group or add totals.
To edit the default values, you must select the group member in the Row or Column Groups pane, and change the
property values in the Properties window. If the properties pane is not visible, in the View menu, click Properties
or press F4. The following properties are available:
FixedData. Boolean. For outer row and column headers. Freeze the row group area when scrolling
vertically or the column group area when scrolling horizontally in a renderer such as HTML.
HideIfNoRows. Boolean. For static members only. If set, Hidden and ToggleItem are ignored. Hide this
member if the Tablix data region contains no rows of data.
KeepTogether.
KeepWithGroup. Boolean. For static row members only. Where possible, keep this row with the previous
or following sibling dynamic member, if it is not hidden.
RepeatOnNewPage. Boolean. For static row members only and where KeepWithGroup is not None. Where
possible, repeat this static row on every page that has at least one instance of the dynamic member
specified by KeepWithGroup.
Hidden. Boolean. Indicates whether the row or column should be initially hidden.
ToggleItem. String. The name of the text box to which to add the toggle image. The text box must be in the
same group scope or a containing scope.
For more information about how this behavior can be controlled on a Tablix data region, see Controlling the
Tablix Data Region Display on a Report Page (Report Builder and SSRS).
Not every static member has a header that corresponds to a cell on the design surface. In the Grouping
pane, the following convention indicates whether a static member has no header:
Static Indicates a static member with a header cell.
(Static) Indicates a static member with no header cell, known as a hidden static.
See Also
Tables, Matrices, and Lists (Report Builder and SSRS)
Expressions (Report Builder and SSRS)
Filter, Group, and Sort Data (Report Builder and SSRS)
Project Property Pages Dialog Box
5/30/2017 • 3 min to read • Edit Online
Use the project property pages to configure deployment properties for a Report Server project. To open this dialog
box, from the Project menu, click <Report Project Name>Properties.
After you define configuration properties, you can select a configuration from the Solution Configurations dropdown list on the toolbar.
Options
Configuration
Select the configuration to edit. Initially, the following configurations are available: Debug, DebugLocal, and
Release. The active configuration appears first, for example, Active(Debug).
To see properties for more than one configuration at the same time, select All Configurations or Multiple
Configurations.
To create additional configurations, click Configuration Manager on the toolbar.
Configuration Manager
Manage configurations for the entire solution or to add additional configurations. For more information, see the
Microsoft Visual Studio documentation.
OutputPath
Type or paste the path to store the report definition used in build verification, deployment, and preview of reports.
The path must be different than the path that you use for the project and a relative path that is a child folder under
the path of the project.
NOTE
You can use multiple configurations to switch among paths depending on the task you perform.
ErrorLevel
Type the severity of the build issues that are reported as errors. Issues with severity levels less than or equal to the
value of ErrorLevel are reported as errors; otherwise, the issues are reported as warnings. Any error will cause the
build task to fail. The valid severity levels are 0 through 4 inclusively. The default value is 2.
StartItem
Select the report that is displayed in the Web browser after the project is published to the report server or in the
preview window when the project is run locally. A start item is required for configurations that build but do not
deploy the project and for using the Debug command (F5). It is required for configurations that deploy the
project.
OverwriteDataSources
Select True to overwrite the data source on the server with the data source in the project when the reports are
published. Select False to leave the existing data source on the server.
TargetServerVersion
Select either the appropriate version of Reporting Services or select Detect Version to automatically determine
the version installed on the server identified by the TargetServer URL property. The default value is SQL Server
2016.
TargetDataSourceFolder
The name of the folder in which to store the published shared data sources. If you do not specify a folder, the data
source is published to the same folder as the report. If the folder does not exist on the report server, Report
Designer creates the folder when the reports are published.
When publishing to a report server running in native mode, specify the full path of the folder hierarchy starting at
the root. For example, Folder1/Folder2/Folder3.
When publishing to a report server running in SharePoint integrated mode, use a URL to the SharePoint library.
For example, http:\\<servername>\<site>\Documents\MyFolder .
TargetReportFolder
The name of the folder in which to store the published reports. By default, this is the name of the report project. If
the folder does not exist on the report server, Report Designer creates the folder when the reports are published.
When publishing to a report server running in native mode, specify the full path of the folder hierarchy starting at
the root. If a folder is located within another folder, include a path to the folder starting at the root, such as
Folder1/Folder2/Folder3.
When publishing to a report server running in SharePoint integrated mode, use a URL to SharePoint library. For
example, http:\\<servername>\\<site>\Documents\MyFolder .
TargetServerURL
The URL of the target report server. Before you publish a report, you must set this property to a valid report server
URL.
When publishing to a report server running in native mode, use the URL of the virtual directory of the report
server. For example, http:\\<server>\reportserver . This is the virtual directory of the report server, not Report
Manager. By default, the report server is installed in a virtual directory named "reportserver".
When publishing to a report server running in SharePoint integrated mode, use a URL to a SharePoint top-level
site or subsite. If you do not specify a site, the default top-level site is used. For example:
http:\\<servername>
,
http:\\<servername\<site>
http:\\<servername>\<site>\<subsite>
.
Next steps
Publish Reports
Publish a Report to a SharePoint Library
Set Deployment Properties (Reporting Services)
Report Designer F1 Help
More questions? Try asking the Reporting Services forum
Reporting Services Login Dialog Box (SSRS)
3/24/2017 • 1 min to read • Edit Online
Use the Reporting Services Login dialog box to provide credentials to publish reports to the report server.
Note If this is the first time you have published a report to a report server since set you set the deployment
property TargetServerURL for a project, verify that the server name includes server and not reports. For
example, http://localhost/reportserver , and not http://localhost/reports . Specifying the reports directory
on the local server instead of the reportserver directory indirectly causes this dialog box to open. For more
information about setting TargetServerURL, see Set Deployment Properties (Reporting Services).
Options
Server
Displays the name of the report server. For example, http://localhost/reportserver . For report servers that use a
different port than default port 80, include the port number. For example, http://localhost:81/reportserver .
User name
Type the user name to log in to the Web service.
Password
Type the password to log in to the Web service.
See Also
Data Connections, Data Sources, and Connection Strings (Report Builder and SSRS)
Specify Credential and Connection Information for Report Data Sources
Report Designer F1 Help
Reporting Services in SQL Server Management
Studio (SSRS)
3/24/2017 • 1 min to read • Edit Online
Report server administrators can use SQL Server Management Studio to:
Enable features, set server defaults, and manage running jobs.
View and create custom reports. In Object Explorer, many nodes display a set of standard reports that are
installed with Management Studio. You must have administrator permissions. The schema of a custom
report must match the schema of the installed reports. For more information, see Custom Reports in
Management Studio and Find the Report Definition Schema Version (SSRS).
Report authors can use Management Studio to:
Visualize spatial data from a query result set for a map report. After you run the query, use the Spatial
results tab in the result set pane. For more information, see View Spatial Data in Object Explorer.
This section contains step-by-step instructions for performing various reporting tasks using Management
Studio. Creating and managing shared schedules can also be performed using Report Manager.
In This Section
Connect to a Report Server in Management Studio
Set Report Server Properties (Management Studio)
Create, Delete, or Modify a Role (Management Studio)
Cancel Report Server Jobs (Management Studio)
See Also
Report Server in Management Studio F1 Help
Introducing SQL Server Management Studio
Set Report Server Properties (Management Studio)
3/24/2017 • 1 min to read • Edit Online
You can set report server system properties in SQL Server Management Studio to enable features or set server
defaults.
To open the Advanced Server Properties page
1. Start Management Studio and connect to a report server instance.
2. Right-click the report server node, and select Properties. Click Advanced to open the properties page. See
Server Properties (Advanced Page) - Reporting Services for a description of each property.
See Also
Connect to a Report Server in Management Studio
Report Server System Properties
Connect to a Report Server in Management Studio
6/19/2017 • 5 min to read • Edit Online
SQL Server Management Studio provides Object Explorer, which allows you to connect to any server in the SQL
Server family and graphically browse its contents. For Reporting Services, you can use Object Explorer to do the
following:
Enable report server features.
Set server defaults and configure role definitions.
Manage jobs that are running.
Manage job schedules.
You can connect to a native mode report server or a report server that runs in SharePoint integrated
mode. Connection syntax and the types of operations you can perform will vary depending on the server
mode of the report server and your permissions. If you have trouble connecting to a report server or
performing specific tasks, it might be that you have insufficient permissions or you specified the report
server name incorrectly. For more information about permissions and connection syntax, see the table at
the end of this topic.
Note that you cannot use Object Explorer to view or manage report server content. Content management
is performed through Report Manager if the report server runs in native mode or through a SharePoint
site if the report server runs in SharePoint integrated mode.
Object Explorer allows you to open connections to multiple server instances in the same workspace as
along as the servers are registered in the same server group. Before you can connect to a report server
instance in Management Studio, the server must be registered. If the report server is already registered,
you can skip this step. Instructions for registering report servers are provided at the end of this topic.
To connect to a native mode report server
1. If Object Explorer is not already open it, select it from the View menu.
2. Click Connect to view the list of server types, and then select Reporting Services.
3. In the Connect to Server dialog box, enter the name of the report server instance. Report server instance
names are based on SQL Server instance names. By default, the instance name of a local report server
instance is just the computer name. If you installed the report server as a named instance, use this syntax
to specify the server: <servername>[\].
4. Select the authentication type. If you are using Windows Authentication, you must connect using your
credentials. If you select Basic authentication or Forms authentication, type the account and password.
5. Click Connect. The report server appears in Object Explorer.
6. Right-click the server node to set system properties and server defaults. For more information, see Set
Report Server Properties (Management Studio).
To connect to a SharePoint integrated mode report server
1. If Object Explorer is not already open it, select it from the View menu.
2. Click Connect to view the list of server types, and then select Reporting Services.
3. In the Connect to Server dialog box, enter a URL to a SharePoint site. The following example illustrates
the syntax:
http://<web server>/sites/<site>
.
4. Select the authentication type. If you are using Windows Authentication, you must connect using your
credentials. If you select Basic authentication or Forms authentication, type the account and password.
5. Click Connect. The report server appears in Object Explorer.
6. Right-click the server node to set system properties and server defaults. For more information, see Set
Report Server Properties (Management Studio).
To register a report server
1. If you cannot connect to a report server, you either do not have permission to access it or it must be
registered. To register the server, click Registered Servers on the View menu,
2. Click the Reporting Services icon.
3. Right-click Reporting Services, point to New, and then click Server Registration. The New Server
Registration dialog box is displayed.
4. For Server name, enter a value. The value that you must specify will vary depending on the server mode:
For a native mode report server, type the name of the report server instance. Report server instance
names are based on SQL Server instance names. By default, the instance name of a local report
server instance is just the computer name. If you installed the report server as a named instance,
use this syntax to specify the server: <servername>[\].
For a report server that runs in SharePoint integrated mode, the server to connect to is the
SharePoint site with which the report server is connected. Connecting to the SharePoint site is
necessary so that you can view the permission levels that control access to report server content
and operations. You can specify any site in the site collection. The following example illustrates the
syntax: http://mysharepointsite .
5. For Authentication, select which authentication mode to use to access the Web server. You must choose
the authentication mode that the report server is already using.
If you are using default security, choose Windows Authentication.
If you installed and deployed a custom security extension, choose Forms Authentication.
If you configured the report server to use Basic authentication, choose Basic Authentication.
If the report server is configured for SharePoint integrated mode, choose Windows
Authentication.
6. Click Test to verify the connection.
7. When prompted, click OK, and then click Save.
Connection Syntax and Permissions
The following table summarizes the connection syntax, operations, and permissions required to perform specific
operations.
When you specify Reporting Services as the Server Type in the Connect to Server dialog box, you can specify
either a report server name or an endpoint to the Web service.
CONNECT TO
TASKS
PERMISSIONS
Native mode report server, connected
as the default or named instance:
View and set server properties and
defaults.
Assigned to the System Administrator
role.
<server name><_instance>
View and cancel jobs.
The connection to the report server is
made through the Report Server WMI
provider.
Create and manage shared schedules.
Native mode report server, connected
as the default or named instance,
through the endpoint to the Report
Server Web service:
View and set server properties and
defaults.
http://<servername>/reportserver
Create, modify, or delete role
definitions.
Assigned to the System Administrator
role.
View and cancel jobs.
Create and manage shared schedules.
Specifying a URL to the report server
provides an alternate way to connect
to the report server.
Create, modify, or delete role
definitions.
SharePoint integrated mode report
server, connected through the
SharePoint site:
View and set server properties and
defaults.
Full Control level of permission on the
SharePoint site to which you are
connected.
View and cancel jobs.
http://<webserver>/<SharePointSite>
Create and manage shared schedules
defined for the site to which you are
connected.
View the permission levels defined for
the site to which you are connected.
SharePoint integrated mode report
server, connected through the name of
the report server instance:
View and set server properties and
defaults.
Full Control level of permission on the
SharePoint site that is integrated with
the report server.
View and cancel jobs.
<server name><_instance>
See Also
Configure a Report Server Database Connection (SSRS Configuration Manager)
Reporting Services in SQL Server Management Studio (SSRS)
Notice that when you connect to the
report server rather than the
SharePoint site, the number of tasks
that you can perform is significantly
reduced. This is because the report
server can only return application data
that is stored or managed in the report
server database, and not in the
SharePoint configuration and content
databases.
Delete an Item (Management Studio)
3/24/2017 • 1 min to read • Edit Online
When connected to a report server instance in SQL Server Management Studio, you can delete role definitions and
shared schedules. You cannot delete reports, models, or other items on a report server. To delete report server
content, use Report Manager instead. Or, if the report server is configured for SharePoint integrated mode, use the
item management features in the SharePoint library that contains your content.
To delete an item in the report server folder namespace
1. In ObjectExplorer, expand a report server node. Navigate to the folder containing the item you want to
delete.
2. Expand the folder.
3. Right-click the item, and click Delete.
4. When prompted, Click OK.
See Also
Connect to a Report Server in Management Studio
Delete Catalog Items (Management Studio)
Reporting Services in SQL Server Management Studio (SSRS)
Report Server in Management Studio F1 Help
3/24/2017 • 1 min to read • Edit Online
This section includes topics about the dialog boxes in SQL Server Management Studio that can be used to
manage report servers.
In This Section
Cancel Report Server Jobs
Delete Catalog Items
Job Properties Page
New Shared Schedule
New System Role
New User Role
Schedule Properties (General Page)
Schedule Properties (Reports Page)
Server Properties (General Page)
Server Properties (Execution Page)
Server Properties (History Page)
Server Properties (Logging Page)
Server Properties (Security Page)
Server Properties (Advanced Page)
System Role Properties
User Role Properties
See Also
Feature Reference (Reporting Services)
Use SQL Server Management Studio
Cancel Report Server Jobs (Management Studio)
3/24/2017 • 1 min to read • Edit Online
Use the Cancel Report Server Jobs dialog box to view or cancel in-progress reports. This dialog box shows all
jobs that are currently running on the report server. Although you cannot pause or restart jobs that are currently
processing, you can cancel all jobs or individual jobs if they are taking too long to complete.
You can cancel user jobs and system jobs.
A user job is any job that is initiated by an individual user. This includes running a report on-demand,
manually creating a report history snapshot, or manually creating report execution snapshot. An in-progress
standard subscription is also a user job.
A system job is one that is initiated by the report server. System jobs include scheduled report processing.
To open this page, start SQL Server Management Studio, connect to a report server, right-click Jobs, and
then click Cancel All Jobs. You can also open Jobs, right-click a job that is running on the report server,
and select Cancel Job(s).
Before cancelling a job, you can view its properties to determine when the job started. For more
information, see Job Properties (Management Studio).
NOTE
This feature is not supported in SQL Server Express with Advanced Services. The page does not appear when you are running
SQL Server Express.
Options
Name
Shows the name of the report. Subscriptions are identified by their descriptions.
Type
Valid values are User and System.
Start Time
Shows when the job started.
User Name
For jobs that are initiated by a user, this column shows the name of the user.
Status
Shows the status of the job. Valid values are New and Running. Status is always New when the job begins. After
60 seconds, status changes to Running. You must refresh the page to pick up the change.
OK
Cancel a single job or multiple jobs. The jobs are cancelled immediately and cannot be resumed. If you mistakenly
cancel a job, you must request the report or subscription again to start a new job.
See Also
Report Server in Management Studio F1 Help
Connect to a Report Server in Management Studio
Manage a Running Process
Delete Catalog Items (Management Studio)
3/24/2017 • 1 min to read • Edit Online
Use this page to delete shared schedules and role definitions.
If you delete a shared schedule that is used by multiple reports and subscriptions, the report server will create
individual schedules for each report and subscription that previously used the shared schedule. Each new
individual schedule will contain the date, time, and recurrence pattern that was specified in the shared schedule.
Note that Reporting Services does not provide central management of individual schedules. If you delete a shared
schedule, you will now need to maintain the schedule information for each individual item. Before deleting a
shared schedule, use the Reports page to determine which reports are currently using the shared schedule.
For role definitions, you can only delete those that are not actively used in a role assignment. If you try to delete a
role that is currently in use, the report server will not delete the role and you will see an error message to that
effect. If this page contains a single role definition that is not currently in use, it will be deleted when you click OK. If
this page contains multiple roles, you cannot select which roles to keep or remove. All unused role definitions will
be deleted when you click OK.
You cannot undo a delete operation. If you want to recover an item that you deleted, you must either recreate it or
restore a backup copy of the report server database.
Options
Name
Specifies the name of the item you are deleting.
Type
Shows the type of item you are deleting.
Owner
Shows the name of the owner. In most cases, this is System.
Status
Shows progress information for a delete operation.
Error
Displays an error code if an error occurs while deleting an item.
See Also
Delete an Item (Management Studio)
Report Server in Management Studio F1 Help
Create, Modify, and Delete Schedules
Job Properties (Management Studio)
3/24/2017 • 1 min to read • Edit Online
Use the Job Properties page to view information about an in-progress report or subscription before you cancel it.
To open this page, start SQL Server Management Studio, connect to a report server, and open the Jobs folder.
Right-click a job that is running, and then click Properties.
NOTE
This feature is not supported in SQL Server Express with Advanced Services. The page does not appear when you are running
SQL Server Express.
Tasks
Before you can view information about a job, refresh the page to retrieve information about jobs that are currently
running on the report server:
1. Open the report server folder.
2. Right-click Jobs, and then click Refresh.
3. If a job is listed, right-click the job, and then click Properties.
Options
Job ID
A GUID that is assigned to a job while it is processing. The value is randomly generated each time a report or
subscription runs.
Job Status
Valid values are New and Running. Status is always New when the job begins. After 60 seconds, status changes
to Running. You must refresh the page to pick up the change.
Job Type
Valid values are User and System. A user job is any job that is initiated by an individual user. This includes running
a report on-demand, manually generating a report history snapshot, or manually creating a report execution
snapshot. An in-progress standard subscription is also a user job. A system job is one that is initiated by the report
server. System jobs include report processing that is triggered by a schedule.
Job Action
For reports, this column shows which report execution processes are underway. This value is always Render.
Job Description
Reporting Services does not provide job descriptions by default.
Server Name
Shows the name of the report server that is processing the job. If you configured a scale-out deployment, this
value will show which server is processing the job.
Report Name
Shows the name of the report. Subscriptions are identified by their descriptions.
Report Path
Shows the path of the report in the report server folder hierarchy.
Start Time
Shows when the process started.
User Name
For processes initiated by a user, this column shows the name of the user. For system jobs, this is the name of the
report server.
See Also
Report Server in Management Studio F1 Help
Connect to a Report Server in Management Studio
Manage a Running Process
New Shared Schedule (Management Studio)
4/6/2017 • 2 min to read • Edit Online
Use this page to create a shared schedule to run published reports and subscriptions. Shared schedules can be
used in place of report-specific or subscription-specific schedules. Centralized schedule information and the ability
to pause and resume scheduled operations are two key features that distinguish shared schedules from itemspecific schedules.
Not all frequency combinations can be supported in a single schedule. For example, if you want to run a report at
12:00 P.M. and 4:00 P.M. every Friday, you must create two daily schedules that specify a Friday run date, one with
a start time of 12:00 P.M. and another with a start time of 4:00 P.M.
Schedule processing is based on the local time of the report server that hosts and processes the schedule.
To open this page, start SQL Server Management Studio, connect to a report server, right-click Shared Schedule,
and select New Schedule. To save the schedule, SQL Server Agent service must be running.
NOTE
This feature is not available in every edition of SQL Server. For a list of features that are supported by the editions of SQL
Server, see Features Supported by the Editions of SQL Server 2012 (http://go.microsoft.com/fwlink/?linkid=232473).
Options
Name
Type a name for the shared schedule. This name appears in drop-down lists when users select a shared schedule
for reports and subscriptions. Be sure to provide a descriptive name that fits easily within a list and that easily
distinguishes one shared schedule from another. A name must contain at least one alphanumeric character. It can
also include spaces and some symbols. Do not use the following characters when specifying a name:
;?:@&=+,$/*<>
"/
Begin running this schedule on
Specify a start date for this schedule.
Stop this schedule on
Specify an expiration date for this schedule.
Type
Specifies whether the recurrence pattern is based primarily on hours, days, weeks, or months.
Hour (Recurrence Pattern)
Select options to run a scheduled operation in intervals of an hour (for example, to run a report every 6 hours). You
can specify the interval in hours and minutes.
Day (Recurrence Pattern)
Select options to run a scheduled operation in intervals of days (for example, to run a report every 2 days). You can
specify the interval in days and at the hour and minute you want the schedule to run.
Week (Recurrence Pattern)
Select options to run a scheduled operation in intervals of a week or when the pattern that you want to repeat is
based on weeks (for example, to run a report every other week). You can specify a weekly schedule to the day,
hour, and minute that you want the schedule to run.
Month (Recurrence Pattern)
Select options to run a scheduled operation in intervals of a month or when the pattern that you want to repeat is
based on months. You can specify a monthly schedule to the day, hour, and minute that you want the schedule to
run. You can omit specific months from the schedule.
Once
Select this option to create a schedule that runs only once, on a specific date and time.
See Also
Report Server in Management Studio F1 Help
Connect to a Report Server in Management Studio
Create, Modify, and Delete Schedules
Schedules
Report Server in Management Studio F1 Help
New System Role (Management Studio)
4/6/2017 • 1 min to read • Edit Online
Use this page to create a system-level role definition. A system role definition specifies a set of system-level tasks
that apply to a report server as whole.
NOTE
Role definitions are used only on a report server that runs in native mode. If the report server is configured for SharePoint
integration, this page is not available.
Options
Name
Type the name of the role definition. A role definition name must be unique within the report server namespace. A
name must contain at least one alphanumeric character. It can also include spaces and some symbols. Do not use
the following characters when specifying a name:
;?:@&=+,$/*<>
"/
Description
Provide a description that explains how to use the role and enumerates what the role supports.
Task
Select the system-level tasks that can be performed through this role. You cannot create new tasks or modify the
existing tasks that are supported by Reporting Services. You cannot choose item-level tasks for a system role
definition.
Task Description
Shows a description of the task that enumerates the operations or permissions that the task supports.
See Also
Report Server in Management Studio F1 Help
Role Definitions
New User Role (Management Studio)
4/6/2017 • 1 min to read • Edit Online
Use this page to create an item-level role definition. An item-level role definition is a named collection of tasks that
enumerate the tasks a user can perform in relation to folders, reports, models, resources, and shared data sources.
An example of an item-level role definition is the predefined Browser role that identifies the kinds of actions a
report end user might require for navigating folders and viewing reports.
Role definitions are intended to be few in number. Most organizations only require a few role definitions. However,
if the predefined role definitions are insufficient, you can vary them or create new ones.
NOTE
Role definitions are used only on a report server that runs in native mode. If the report server is configured for SharePoint
integration, this page is not available.
Options
Name
Type the name of the role definition. A role definition name must be unique within the report server namespace. A
name must contain at least one alphanumeric character. It can also include spaces and some symbols. Do not use
the following characters when specifying a name:
;?:@&=+,$/*<>
"/
Description
Type a description that explains how to use the role and enumerates what the role supports.
Task
Select the tasks that can be performed through this role. You cannot create new tasks or modify the existing tasks
that are supported by Reporting Services. Only item-level tasks can be used in an item-level role definition.
Task Description
Shows a description of the task that enumerates the operations or permissions that the task supports.
See Also
Report Server in Management Studio F1 Help
Role Definitions
Schedule Properties (General Page)
3/24/2017 • 2 min to read • Edit Online
Use the Reporting Services page in SQL Server Management Studio to view or modify a shared schedule. Shared
schedules can be used in place of report-specific or subscription-specific schedules. Changes to the schedule are
applied after you save the schedule. Editing a schedule has no effect on jobs that are currently in progress. If you
edit a schedule while it is being used, all currently processing reports and subscriptions triggered from that
schedule will be allowed to finish.
Not all frequency combinations can be supported in a single schedule. For example, if you want to run a report at
12:00 P.M. and 4:00 P.M. every Friday, you must create two daily schedules that specify a Friday run date, one with
a start time of 12:00 P.M. and another with a start time of 4:00 P.M.
Schedule processing is based on the local time of the report server that hosts and processes the schedule.
To open this page: 1) Start SQL Server Management Studio. 2) Connect to a report server. 3) Expand the Shared
Schedules folder. 4) Right-click a shared schedule, and select Properties.
NOTE
This feature is not available in every edition of SQL Server and this page does not appear when you are running an edition
which does not have this feature. For a list of features that are supported by the editions of SQL Server, see Features
supported by the edition in SQL Server 2016.
Options
Name
Specifies the name for the shared schedule.
Begin running this schedule on
Specifies a start date for this schedule.
Stop this schedule on
Specifies an expiration date for this schedule.
Type
Specifies whether the recurrence pattern is based primarily on hours, days, weeks, months, or only runs once.
Hour (Recurrence Pattern)
Specifies options for running a scheduled operation in intervals of an hour (for example, to run a report every 6
hours). You can specify the interval in hours and minutes.
Day (Recurrence Pattern)
Specifies options for running a scheduled operation in intervals of days (for example, to run a report every 2 days).
You can specify the interval in days and at the hour and minute you want the schedule to run.
Week (Recurrence Pattern)
Specifies options for running a scheduled operation in intervals of a week or when the pattern that you want to
repeat is based on weeks (for example, to run a report every other week). You can specify a weekly schedule to the
day, hour, and minute that you want the schedule to run.
Month (Recurrence Pattern)
Specifies options for running a scheduled operation in intervals of a month or when the pattern that you want to
repeat is based on months. You can specify a monthly schedule to the day, hour, and minute that you want the
schedule to run. You can omit specific months from the schedule.
Once
Specifies a schedule that runs only once, on a specific date and time.
See Also
Report Server in Management Studio F1 Help
Connect to a Report Server in Management Studio
Create, Modify, and Delete Schedules
Schedules
Schedule Properties (Reports Page)
3/24/2017 • 1 min to read • Edit Online
Use the Reporting Services schedule properties page in SQL Server Management Studio to view a list of all reports
that use the specific shared schedule. Schedules can be used to refresh report snapshots, generate report history,
trigger a subscription, or expire a cached copy of the report. To find out how the schedule is used, view the
property and subscription information of the report.
Although this page shows each report that uses the shared schedule, it does not indicate how many times the
shared schedule is used within that single report. For example, suppose 20 different subscribers to the Company
Sales report all use the same shared schedule to trigger subscription processing. In this case, the Company Sales
report will only appear once in this list, even though the report has 20 references to the shared schedule.
To open the schedule properties page:
1.
2.
3.
4.
5.
Start SQL Server Management Studio.
Connect to a report server.
Open the Shared Schedules folder.
Right-click a shared schedule, select Properties.
click Reports.
You can also manage shared schedules from the Site Settings of the Reporting Services Web Portal.
NOTE
This feature is not available in every edition of SQL Server. For a list of features that are supported by the editions of SQL
Server, see Features Supported by the edition of SQL Server 2016.
Options
Folder
Specifies the path of the report.
Report
Specifies the name of the report that uses the schedule.
See Also
Create, Modify, and Delete Schedules
Schedules
Report Server in Management Studio F1 Help
Connect to a Report Server in Management Studio
Configure General Properties for a Report (Report Manager)
Report Server Properties (General Page)
3/24/2017 • 1 min to read • Edit Online
Use this page to view or modify the title used in Report Manager, enable or disable My Reports, select a role
definition for My Reports security, and enable or disable the client print control.
To open this page: 1) Start SQL Server Management Studio 2) Connect to a report server instance. 3) Right-click
the report server name, and then select Properties.
The server mode determines which server properties you can set. If you are managing a report server that is
configured for SharePoint integrated mode, you cannot enable My Reports or set the title for the web portal.
Options
Name
Type a name that appears on top of the web portal. By default, this value is SQL Server Reporting Services. The
name that you specify appears only in Report Manager.
Version
This property is read-only. Specifies the version of SQL Server Reporting Services that you are using.
Edition
This property is read-only. Specifies the current report server instance. Report Manager is not available in every
edition of Microsoft SQL Server. For a list of features that are supported by the editions of SQL Server, see Features
Supported by the Editions of SQL Server 2016.
Authentication Mode
This property is read-only. It identifies the types of authentication requests accepted by the report server instance.
To change the authentication mode, you must edit the RSReportServer.config file. For more information, see
Authentication with the Report Server.
URL
This property is read-only. Specifies the URL to the Report Server Web service. This value is specified in the
Reporting Services Configuration tool. For more information, see Configure a URL (SSRS Configuration Manager).
Enable a My Reports folder for each user
Make My Reports available to users. This option is only available for native mode report servers.
Select the role to apply to each My Reports folder
Specify a role definition to use for My Reports security. The role definition identifies the set of tasks that are
supported in each My Reports folder.
See Also
Set Report Server Properties (Management Studio)
Connect to a Report Server in Management Studio
Enable and Disable My Reports
Report Server in Management Studio F1 Help
Secure My Reports
Server Properties (Execution Page)
3/24/2017 • 1 min to read • Edit Online
Use this page to set a timeout value for report execution. This value applies to all reports that are processed by the
current report server instance. You can override this value for individual reports. The value you specify must
accommodate all report processing that occurs on the report server, plus query processing performed on the
database server when the report server retrieves data that is used in the report.
To open this page, start SQL Server Management Studio, connect to a report server instance, right-click the report
server name, and select Properties. Click Execution to open this page.
Options
Do not timeout report execution
Allow a report server unlimited time to complete report processing.
Limit report execution to the following number of seconds
Set a time constraint on report execution. The time period starts when the report is requested. If the time period
ends before the report is fully processed, the report server cancels the process and any in-process queries to
external data sources.
See Also
Set Report Server Properties (Management Studio)
Connect to a Report Server in Management Studio
Set Report Processing Properties
Setting Time-out Values for Report and Shared Dataset Processing (SSRS)
Report Server in Management Studio F1 Help
Server Properties (History Page)
3/24/2017 • 1 min to read • Edit Online
Use this Reporting Services page in SQL Server Management Studio to set a default value for the number of copies
of report history to retain. The default value provides an initial setting that establishes report history limits for all
reports. You can vary these settings for individual reports.
Report history is a collection of report snapshots that include report data and layout that is current for the report at
the time the snapshot is created. You can use report history to keep a copy of a report as it was on a specific date or
time. You can create and manage report history for individual reports that run on a native mode report server or a
report server that is configured for SharePoint integrated mode.
Report history snapshots are stored in the report server database. If you keep an unlimited number of snapshots,
be sure to periodically check the database size to ensure it is not growing too fast or consuming too much disk
space.
To open this page: 1) Start SQL Server Management Studio. 2) Connect to a report server instance. 3) Right-click
the report server name, and select Properties. 4) Click History to open this page.
Options
Keep an unlimited number of snapshots in report history
Retain all report history snapshots. You must manually delete snapshots to reduce the size of report history.
Limit the copies of report history
Retain a set number of report history snapshots. When the limit is reached, older copies are removed from report
history to make room for newer copies.
If you limit report history later, when the existing report history exceeds the limit you specify, the report server
reduces the existing report history to the new limit. The oldest report snapshots are deleted first. If report history is
empty or below the limit, new report snapshots are added. When the limit is reached, the oldest snapshot is deleted
when a new report snapshot is added.
See Also
Set Report Server Properties (Management Studio)
Connect to a Report Server in Management Studio
Report Server in Management Studio F1 Help
Server Properties (Logging Page)
3/24/2017 • 1 min to read • Edit Online
Use this Reporting Services page in SQL Server Management Studio to set limits on the report execution data that
is collected by a report server. Execution data is stored internally in the report server database. You can track report
activity for report server that runs in native mode or SharePoint integrated mode. If the report server is part of a
scale-out deployment, the report execution log maintains a record of all report activity for the entire deployment in
a single log file.
To open this page: 1) Start SQL Server Management Studio 2) Connect to a report server. 3) Right-click the report
server name and select Properties. 4) Click Logging to open this page.
Options
Enable report execution logging
Click to create and store information about report activity on the server. If this option is enabled, the report server
will track which reports are used, the frequency of report processing, the type of report operation that was
performed, the output format, and who ran the report. For more information about additional data points that are
captured in the log, see Report Server ExecutionLog and the ExecutionLog3 View.
Remove log entries older than this number of days
Specify the number of days after which log entries will be trimmed from the report execution log. The default value
is 60 days.
See Also
Set Report Server Properties (Management Studio)
Connect to a Report Server in Management Studio
Reporting Services Log Files and Sources
Report Server in Management Studio F1 Help
Report Server ExecutionLog and the ExecutionLog3 View
Server Properties (Security Page) - Reporting
Services
3/24/2017 • 1 min to read • Edit Online
Use this Reporting Services page in SQL Server Management Studio to turn off features that can potentially
compromise a report server. Turning off these features will limit some functionality, but can improve the overall
security of the report server by mitigating specific threats.
To open this page: 1) Start SQL Server Management Studio. 2) Connect to a report server instance. 3) Right-click
the report server name, and select Properties. 4) Click Security to open this page.
Options
Enable Windows integrated security for report data sources
Specify whether a connection to a report data source can be made using the Windows security token of the user
who requested the report.
If you turn off this feature, the Windows Integrated Security feature in the report data source property pages will be
unavailable. If report data sources are configured for Windows integrated security and you subsequently turn off
this feature, the report server will immediately update all data source connection properties to prompt for
credentials.
Enable Ad Hoc Reporting
Specify whether users can perform ad hoc queries from a Report Builder report, where new reports are
automatically generated when a user clicks data of interest.
Setting this option determines whether the EnableLoadReportDefinition property on the report server is set to
True or False. If you clear this option, the property will be set to False and report server will not generate
clickthrough reports that are created during data exploration. All calls to the LoadReportDefinition method will
be blocked.
Turning off this option mitigates a threat whereby a malicious user launches a denial of service attack by
overloading the report server with LoadReportDefinition requests.
See Also
Set Report Server Properties (Management Studio)
Connect to a Report Server in Management Studio
Specify Credential and Connection Information for Report Data Sources
Report Server in Management Studio F1 Help
Server Properties (Advanced Page) - Reporting
Services
3/24/2017 • 4 min to read • Edit Online
Use this page to set system properties on the report server. There are a number of ways to set system properties.
This tool provides a graphical user interface so that you can set properties without having to write code.
To open this page, start SQL Server Management Studio, connect to a report server instance, right-click the report
server name, and select Properties. Click Advanced to open this page.
Options
EnableMyReports
Indicates whether the My Reports feature is enabled. A value of true indicates that the feature is enabled.
MyReportsRole
The name of the role used when creating security policies on user's My Reports folders. The default value is My
Reports Role.
EnableClientPrinting
Determines whether the RSClientPrint ActiveX control is available for download from the report server. The valid
values are true and false. The default value is true. For more information about additional settings that are
required for this control, see Enable and Disable Client-Side Printing for Reporting Services.
EnableExecutionLogging
Indicates whether report execution logging is enabled. The default value is true. For more information about the
report server execution log, see Report Server ExecutionLog and the ExecutionLog3 View.
ExecutionLogDaysKept
The number of days to keep report execution information in the execution log. Valid values for this property
include -1 through 2,147,483,647. If the value is -1 entries are not deleted from the Execution Log table. The
default value is 60.
NOTE
Setting a value of 0 will delete all entries from the execution log. A value of -1 will keep the entries of the execution log and
will not be deleted.
SessionTimeout
The length of time, in seconds, that a session remains active. The default value is 600.
SharePointIntegratedMode
This is a read-only property that indicates the server mode. If this value is False, the report server runs in native
mode.
SiteName
The name of the report server site displayed in the page title of the web portal. The default value is SQL Server
Reporting Services. This property can be an empty string. The maximum length is 8,000 characters.
StoredParametersLifetime
Specifies the maximum number of days that a stored parameter can be stored. Valid values are -1, +1 through
2,147,483,647. The default value is 180 days.
StoredParametersThreshold
Specifies the maximum number of parameter values that that can be stored by the report server. Valid values are 1, +1 through 2,147,483,647. The default value is 1500.
UseSessionCookies
Indicates whether the report server should use session cookies when communicating with client browsers. The
default value is true.
ExternalImagesTimeout
Determines the length of time within which an external image file must be retrieved before the connection is timed
out. The default is 600 seconds.
SnapshotCompression
Defines how snapshots are compressed. The default value is SQL. The valid values are as follows:
SQL = Snapshots are compressed when stored in the report server database. This is the current behavior.
None = Snapshots are not compressed.
All = Snapshots are compressed for all storage options, which include the report server database or the file
system.
SystemReportTimeout
The default report processing timeout value, in seconds, for all reports managed in the report server namespace.
This value can be overridden at the report level. If this property is set, the report server attempts to stop the
processing of a report when the specified time has expired. Valid values are -1 through 2,147,483,647. If the value
is -1, reports in the namespace do not time out during processing. The default value is 1800.
SystemSnapshotLimit
The maximum number of snapshots that are stored for a report. Valid values are -1 through 2,147,483,647. If the
value is -1, there is no snapshot limit.
EnableIntegratedSecurity
Determines whether Windows integrated security is supported for report data source connections. The default is
True. The valid values are as follows:
True = Windows integrated security is enabled.
False = Windows integrated security is not enabled. Report data sources that are configured to use Windows
integrated security will not run.
EnableLoadReportDefinition
Select this option to specify whether users can perform ad hoc report execution from a Report Builder report.
Setting this option determines the value of the EnableLoadReportDefinition property on the report server.
If you clear this option, the property will be set to False and report server will not generate clickthrough reports for
reports that use a report model as a data source. Any calls to the LoadReportDefinition method will be blocked.
Turning off this option mitigates a threat whereby a malicious user launches a denial of service attack by
overloading the report server with LoadReportDefinition requests.
EnableRemoteErrors
Includes external error information (for example, error information about report data sources) with the error
messages that are returned for users who request reports from remote computers. Valid values are true and false.
The default value is false. For more information, see Enable Remote Errors (Reporting Services).
EnableReportDesignClientDownload
Specifies whether Report Builder installation package can be downloaded from the report server. If you clear this
setting, the URL to Report Builder will not work. For more information, see Configure Report Builder Access.
EditSessionCacheLimit
Specifies the number of data cache entries that can be active in a report edit session. The default number is 5.
EditSessionTimeout
Specifies the number of seconds until a report edit session times out. The default value is 7200 seconds (2 hours).
EnableTestConnectionDetailedErrors
Indicates whether detailed error messages are sent to the client computer when users test data source connections
using the report server. The default value is true. If the option is set to false, only generic error messages are sent.
See Also
Set Report Server Properties (Management Studio)
Connect to a Report Server in Management Studio
Reporting Services Properties
Report Server in Management Studio F1 Help
Report Server System Properties
Script Deployment and Administrative Tasks
Enable and Disable My Reports
System Role Properties (Management Studio)
3/24/2017 • 1 min to read • Edit Online
Use the System Roles page to view the system role definitions that are currently defined for the report server. A
system role definition contains a named collection of tasks that are performed relative to the entire site, instead of
an individual item. Role definitions are assigned to a user or groups to create a resulting role assignment. The tasks
in the role definition specify what the user or group can do.
Reporting Services has two predefined system role definitions: System Administrator and System User. You can
modify these role definitions by changing the task list, or you can create a new system role that supports a different
combination of tasks. Editing a role definition affects all role assignments that include the role definition.
NOTE
System role assignments are used only on a report server that runs in native mode. If the report server is configured for
SharePoint integration, this page is not available.
Options
Name
Specifies the name of the system role definition.
Description
Shows a description of the system role definition. In SQL Server Management Studio, this description is only visible
in this page. Users who view this item through Report Manager may see this description when browsing the folder
hierarchy.
Task
Lists all system-level tasks that can be selected for this role definition. You can add or remove items from the
predefined task list to define how users access a given item through this role. You cannot create new tasks, and you
cannot modify existing tasks.
Description
Provides information about each task. You cannot modify task descriptions.
See Also
Report Server in Management Studio F1 Help
System-Level Tasks
Tasks and Permissions
Predefined Roles
User Role Properties (Management Studio)
3/24/2017 • 1 min to read • Edit Online
Use this page to view which tasks are included in an item-level role definition. You can also use this page to change
the task list or modify a role description.
An item-level role definition is a named collection of tasks that users perform relative to a specific item (that is, a
folder, report, resource, or shared data source). Role definitions are assigned to a user or group to create a role
assignment in Report Manager. The tasks in the role definition describe what the user or group can do.
Reporting Services includes a number of predefined item-level role definitions that you can work with. You can
modify the role definitions by changing the task list of each one. Editing a role definition affects all role
assignments that include the role definition.
NOTE
User role assignments are used only on a report server that runs in native mode. If the report server is configured for
SharePoint integration, this page displays read-only information about the roles and permission levels that are defined on
the SharePoint site.
Options
Name
Specifies the name of the role definition.
Description
Shows a description of the role definition. In SQL Server Management Studio, this description is only visible in this
page. In Report Manager, this description helps users decide whether to use the role in a role assignment.
Task
Lists all item-level tasks that can be selected for this role definition. You can add or remove items from the
predefined task list to define how users access a given item through this role. You cannot create new tasks, and you
cannot modify existing tasks. The task list of a role definition appears only in SQL Server Management Studio.
Task Description
Provides information about each task. You cannot modify task descriptions.
See Also
Item-Level Tasks
Role Definitions
Report Server in Management Studio F1 Help
Tasks and Permissions
Predefined Roles
Report Builder authoring environment (SSRS)
3/24/2017 • 1 min to read • Edit Online
Report Builder Report Builder is a stand-alone authoring environment for creating Reporting Services paginated
reports outside of Visual Studio. When you design a report, you specify where to get the data, which data to get,
and how to display the data. When you run the report, the report processor takes all the information you have
specified, retrieves the data, and combines it with the report layout to generate the report. You can install it from
the Reporting Services web portal or from the Microsoft Download Center.
Install Report Builder from the Microsoft Download Center.
Benefits of Report Builder
Report Builder enables you to:
Use the Report Builder ribbon to quickly add items your reports, launch table, chart, and map wizards, and
format report data.
Add data from built-in data providers by using query designers that help you specify which data to include
in your report.
Create and use report parameters and other interactive features that enable your report readers to
customize data and vary report presentation.
Create expressions from built-in fields, collections, operators, and functions.
Open reports directly from a report server.
Preview reports that use local or published shared data sources and shared datasets.
Preview reports in HTML or print format.
Export reports to other file formats such as Microsoft Excel.
Save your report and related items to a SharePoint library, a report server, or your local computer.
Report Builder and Report Designer share many features. Read more about Report Builder in SQL Server
2016.
See Also
Install Report Builder
Configure Report Builder Access
Reporting Services Tools
Design Reports with Report Designer (SSRS)
Scripting and PowerShell with Reporting Services
3/24/2017 • 1 min to read • Edit Online
Reporting Services supports a wide range of development and management scenarios through script, including the
rs.exe command line utility, PowerShell cmdlets for SharePoint mode report servers, and leveraging the Reporting
Services object model from PowerShell for both Native and SharePoint mode.
Administrators can write script in Microsoft Visual Basic to automate how they deploy and manage a report
server installation. Administrators can also generate and run Transact-SQL scripts that create, configure, and
update a report server database. Administrators can also use the record and playback script features in SQL
Server Management Studio to automate routine maintenance tasks.
Developers can create custom applications that include script. You can run script that makes calls to the
Report Server Web service. Almost any operation that you can write in managed code can also be written in
script.
Reporting Services supports Microsoft Visual Basic .NET script as the script language that can be processed
by the RS.exe utility, a script host that runs on the report server.
Reporting Services SharePoint mode PowerShell cmdlets and samples
Reporting Services SharePoint mode includes Reporting Services cmdlets for report server administration.
PowerShell cmdlets for Reporting Services SharePoint Mode Includes the following examples:
Create a service application and proxy
Review and update a delivery extension
Get and set Properties of the Reporting Service Application Database, for example database timeout
List Data Extensions
Reporting Services Object model and Powershell samples
PowerShell calling the core object model and for the most part valid for SharePoint and native mode, for example
the migration work, subscription work, and more related samples for subscriptions work in SQL15.
Use PowerShell to Change and List Reporting Services Subscription Owners and Run a Subscription.
Use PowerShell to Create an Azure VM With a Native Mode Report Server.
See the section “Access the WMI classes using PowerShell” in Access the Reporting Services WMI Provider.
RS.exe scripting samples
Sample Reporting Services rs.exe Script to Copy Content between Report Servers.
For additional script, application, and extension examples, see SQL Server Reporting Services Product
Samples.
See Also
RS.exe Utility (SSRS)
Script Deployment and Administrative Tasks
Script with the rs.exe Utility and the Web Service
Script with the rs.exe Utility and the Web Service
3/24/2017 • 1 min to read • Edit Online
Developers and report server administrators can perform operations on a report server through the use of the rs
utility (RS.exe). Using this utility, you can programmatically administer a report server using scripts written with
Microsoft Visual Basic.
Reporting Services scripts can be used to run any of the Report Server Web service operations. Scripting can be
used to copy security to multiple reports on a server, to add and delete items, to copy report server items from one
server to another and more. For more information about the scripting environment, see Run a Reporting Services
Script File. Script files take a certain format and are written in Visual Basic .NET. For more information, see Format a
Reporting Services Script File.
For script samples, see the following:
Sample Reporting Services rs.exe Script to Copy Content between Report Servers.
SQL Server Reporting Services Product Samples.
See Also
Script Deployment and Administrative Tasks
Report Server Web Service
Technical Reference (SSRS)
RS.exe Utility (SSRS)
Format a Reporting Services Script File
3/24/2017 • 1 min to read • Edit Online
A Reporting Services script is a Microsoft Visual Basic .NET code file, written against a proxy that is built on Web
Service Description Language (WSDL), which defines the Reporting Services SOAP API. A script file is stored as a
Unicode or UTF-8 text file with the extension .rss.
The script file acts as a Visual Basic module and can contain user-defined procedures and module-level variables.
For the script file to run successfully, it must contain a Main procedure. The Main procedure is the first procedure
that is accessed when your script file runs. Main is where you can add your Web service operations and run your
user defined subprocedures. The following code creates a Main procedure:
Public Sub Main()
' Your code goes here.
End Sub
The script environment automatically connects to the report server, creates the Web proxy class, and generates a
reference variable (rs) to the Web service proxy object. Individual statements that you create need only refer to the
rs module-level variable to perform any of the Web service operations that are available in the Web service library.
The following Visual Basic code calls the Web service ListChildren method from within a script file:
Public Sub Main()
Dim items() As CatalogItem
items = rs.ListChildren("/", True)
Dim item As CatalogItem
For Each item In items
Console.WriteLine(item.Name)
Next item
End Sub
IMPORTANT
User credentials are managed by the script environment and passed through command prompt arguments through the use
of RS.exe. Although you can use the rs variable to set the authentication of the Web service, it is recommended that you use
the script environment. You do not need to authenticate the Web service in the script file itself. For more information about
authenticating the script environment, see RS.exe Utility (SSRS).
You do not declare namespaces within the script file. The scripting environment makes several useful Microsoft
.NET Framework namespaces available to you: System.Web.Services, System.Web.Services.Protocols,
System.Xml, and System.IO.
For script samples, see SQL Server Reporting Services Product Samples.
See Also
Report Server Web Service
Technical Reference (SSRS)
RS.exe Utility (SSRS)
Run a Reporting Services Script File
3/24/2017 • 1 min to read • Edit Online
Reporting Services script files are run from the command prompt using the Reporting Services script environment
(RS.exe). RS.exe has many command prompt arguments available for you to use. For more information about the
command prompt options, see RS.exe Utility (SSRS). For more script samples, see SQL Server Reporting Services
Product Samples.
Sample Command Lines
Run Script.rss in the script environment designating the target report server. Windows Authentication is
applied by default:
rs –i Script.rss -s http://servername/reportserver
Run Script.rss in the script environment specifying a user name and password for authenticating the Web
service calls:
rs –i Script.rss -s http://servername/reportserver -u myusername -p mypassword
Run Script.rss in the script environment specifying a server time-out of 30 seconds:
rs –i Script.rss -s http://servername/reportserver -l 30
Run Script.rss in the script environment specifying a global script variable called report.
rs –i Script.rss -s http://servername/reportserver -v report="Company Sales"
Run Script.rss in the script environment specifying that the Web service operations in the script file are run
as a batch.
rs –i Script.rss -s http://servername/reportserver -b
See Also
Technical Reference (SSRS)
Script Deployment and Administrative Tasks
5/30/2017 • 9 min to read • Edit Online
Reporting Services supports the use of scripts to automate routine installation, deployment, and administrative
tasks. Deploying a report server is a multi-step process. You must use several tools and processes to configure a
deployment; there is no single program or approach that can be used to automate all the tasks.
Not every step should be automated. In some cases, performing a step manually or through a graphical tool is the
simplest and most effective approach. For example, if you want to deploy a large number of reports and models, it
is better to copy the report server databases rather than write code that recreates report server environment.
Some steps require custom code. For example, configuring the URLs for the Web service and Report Manager can
be automated, but only if you write custom code that makes calls into the Report Server Windows Management
Instrumentation (WMI) provider. If you do not want to write code, you must use the Reporting Services
Configuration tool to perform the step.
To run script that configures a report server, you must be a local administrator on the computer that you are
configuring. For more information, see Configure a Report Server for Remote Administration.
This topic describes recommended approaches for automating specific steps. Several programs and programmatic
interfaces are mentioned; descriptions of each one are provided later in this topic.
Deployment Tasks and How to Automate Them
The following table summarizes the installation and configuration tasks that are necessary for deploying a report
server. You can use the table to match a specific task to an approach that allows you to automate or perform the
task unattended.
TASK
APPROACH
Install Reporting Services.
You can run setup from the command line to perform an
unattended installation.
You can use Setup to both install and configure a report
server, but only if you specify the default configuration option
and your system meets all the requirements for this
installation type. If you cannot install the default
configuration, you must perform a files-only installation.
Configure the service account.
The service account is initially configured through Setup. To
automate changes to the service account as a post-Setup
task, you must write custom code that makes calls into the
Report Server WMI provider. There are no command-prompt
utilities or script templates for configuring the service account
programmatically.
If coding requirements prevent you from automating this
step, you can easily configure the account manually by
running the Reporting Services Configuration tool. For more
information, see Configure a Service Account (SSRS
Configuration Manager).
TASK
APPROACH
Configure the Report Server Web service and Report Manager
URLs.
You must write custom code that makes calls into the Report
Server WMI provider. There are no command line utilities or
script templates for configuring the URLs.
If you want to avoid writing code, you can configure the URLs
manually by running the Reporting Services Configuration
tool. For more information, see Configure a URL (SSRS
Configuration Manager).
Create the report server database.
You must write custom code that makes calls into the Report
Server WMI provider. There are no command-prompt utilities
or script templates for creating the report server databases
and RSExecRole.
If you want to avoid writing code, you can create the
database manually by running the Reporting Services
Configuration tool. For more information, see Create a Native
Mode Report Server Database (SSRS Configuration Manager).
Configure the report server database connection.
If you are changing the connection string, account or
password, or the authentication type, run the rsconfig utility
to configure the connection. For more information, see
Configure a Report Server Database Connection (SSRS
Configuration Manager) and rsconfig Utility (SSRS).
You cannot use rsconfig.exe to create or upgrade the
database. The database and RSExecRole must already exist.
Configure a scale-out deployment.
Choose from the following approaches to automate scale-out
deployment:
- Run the rskeymgmt.exe utility to join report server instances
to an existing installation. For more information, see Add and
Remove Encryption Keys for Scale-Out Deployment (SSRS
Configuration Manager).
- Write custom code that runs against the Report Server WMI
provider.
Backup encryption keys.
Choose from the following approaches to automate
encryption key backup:
- Run the rskeymgmt.exe utility to back up the keys. For more
information, see Back Up and Restore Reporting Services
Encryption Keys.
- Write custom code that runs against the Report Server WMI
provider.
TASK
APPROACH
Configure Report Server E-mail.
Write custom code that runs against the Reporting Services
WMI provider. The provider supports a subset of the e-mail
configuration settings.
Although the RSReportServer.config file includes all the
settings, do not use the file in an automated manner.
Specifically, do not use a batch file to copy the file to another
report server. Each configuration file includes values that are
specific to the current instance. Those values will not be valid
on other report server instances.
For more information about the settings, see Configure a
Report Server for E-Mail Delivery (SSRS Configuration
Manager).
Configure the unattended execution account.
Choose from the following approaches to automate
unattended processing account configuration:
- Run the rsconfig.exe utility to configure the account. For
more information, see Configure the Unattended Execution
Account (SSRS Configuration Manager).
- Write custom code that makes calls into the Report Server
WMI provider.
Deploy existing content on another report server, including
the folder hierarchy, role assignments, reports, subscriptions,
schedules, data sources, and resources.
The best way to re-create an existing report server
environment is to copy the report server database to a new
report server instance.
An alternative approach is to write custom code that recreates
existing report server content programmatically. However, be
aware that subscriptions, report snapshots, and report history
cannot be recreated programmatically.
Some deployments can benefit from using both techniques
together (that is, restore a report server database, and then
run custom code that modifies the report server database for
a specific installation).
For a detailed example, see Sample Reporting Services rs.exe
Script to Copy Content between Report Servers.
For more information about relocating a report server
database, see Moving the Report Server Databases to
Another Computer (SSRS Native Mode). For more information
about creating report serer environment programmatically,
see the section "Using Script to Migrate Report Server
Content and Folders" in this topic.
Tools and Technologies for Automating Server deployment
The following list summarizes the programs and interfaces that can be used to automate deployment and
maintenance tasks:
The Setup program can be run in unattended mode to install and sometimes configure report server
components. You must use the Files-Only installation option to have Setup configure a report server
instance.
The Reporting Services WMI provider and Reporting Services command line utilities can be used for local
and remote server configuration.
The Reporting Services WMI provider exposes classes, properties, and methods that allow you to configure
all aspects of a Reporting Services installation including specifying the service account, configuring URLs,
creating and configuring the report server database, or configuring a report server for e-mail delivery. You
must write custom code or script to use the WMI provider. For more information, see Access the Reporting
Services WMI Provider.
An alternative to writing code is to use the command line utilities (rsconfig.exe and rskeymgmt.exe). You
can write batch files that run the utilities. You can use the utilities to automate some but not all
configuration tasks.
The report server script host tool (rs.exe) can run custom Microsoft Visual Basic code that you might write
to re-create or move existing content from one report server to another. With this approach, you write
script in Visual Basic, save it as an .rss file, and use rs.exe to run the script on the target report server. The
script you write can call the SOAP interface to the Report Server Web service. Deployment scripts are
written using this approach because it allows you to re-create a report server folder namespace and
content, and re-create role-based security.
The SQL Server 2012 release introduced PowerShell cmdlets for SharePoint integrated mode. You can use
PowerShell to configure and administer the SharePoint integration. For more information, see PowerShell
cmdlets for Reporting Services SharePoint Mode.
Use Scripts to Migrate Report Server Content and Folders
You can write scripts that duplicate a report server environment on another report server instance. Deployment
scripts are generally written in Visual Basic and then processed using the report server script host utility.
For a detailed example, see Sample Reporting Services rs.exe Script to Copy Content between Report Servers.
Use scripts to copy folders, shared data sources, resources, reports, role assignments, and settings from one server
to another. You write a script for one report server instance, and then run it on another server to re-create the
report server namespace. If you have multiple report servers in your Reporting Services deployment, you can run
the script on each server individually to configure all servers in the same way.
The following list describes the steps for migrating reports from one server to another.
1. Set your script variable to the URL of the source report server.
2. Use the GetItemDefinition and GetProperties methods to retrieve the report definition and the properties of
the report.
3. Set the URL to point to the destination server.
4. Use CreateCatalogItem method, passing the properties returned from GetProperties and the report
definition returned by GetItemDefinition.
By using a combination of get and create methods, you can perform similar steps to migrate settings,
folders, shared data sources, and resources. For more information about the methods available to you, see
Technical Reference (SSRS).
NOTE
Scripts run under the Microsoft Windows credentials of the user running the script unless credentials are explicitly set.
For more information about how to format and run a script file, see Script with the rs.exe Utility and the Web
Service.
Using Scripts to Set Server Properties
You can write scripts that set system properties on the report server. The following Visual Basic .NET script shows
one way to set properties. This example disables the RSClientPrint ActiveX control, but you can replace
EnableClientPrinting and False with any valid property name and value. To view a complete list of server
properties, see Report Server System Properties.
To use the script, save it to a file that has an .rss extension, and then use the rs.exe command prompt utility to run
the file on the report server. The script is not compiled, so it is not necessary to have an installation of Visual Basic.
This example assumes that you have permissions on the local computer that hosts the report server. If you are not
logged on under an account that has permissions, you must specify account information through additional
command line arguments. For more information, see RS.exe Utility (SSRS).
TIP
For a detailed example, see Sample Reporting Services rs.exe Script to Copy Content between Report Servers.
Public Sub Main()
Dim props(0) As [Property]
Dim setProp As New [Property]
setProp.Name = "EnableClientPrinting"
setProp.Value = “False”
props(0) = setProp
Try
rs.SetSystemProperties(props)
Catch ex As System.Web.Services.Protocols.SoapException
Console.Write(ex.Detail.InnerXml)
Catch e as Exception
Console.Write(e.Message)
End Try
End Sub
Next steps
GenerateDatabaseCreationScript Method (WMI MSReportServer_ConfigurationSetting)
GenerateDatabaseRightsScript Method (WMI MSReportServer_ConfigurationSetting)
GenerateDatabaseUpgradeScript Method (WMI MSReportServer_ConfigurationSetting)
Install SQL Server 2016 from the Command Prompt
Install Reporting Services Native Mode Report Server
Reporting Services Report Server (Native Mode)
Report Server Command Prompt Utilities (SSRS)
Browser Support for Reporting Services and Power View
Reporting Services Tools
More questions? Try asking the Reporting Services forum
Sample Reporting Services rs.exe Script to Copy Content between Report
Servers
5/24/2017 • 14 min to read • Edit Online
This topic includes and describes a sample Reporting Services RSS script that copies content items and settings from one SQL Server Reporting Services
report server to another report server, using the RS.exe utility. RS.exe is installed with Reporting Services, both native and SharePoint mode. The script copies
Reporting Services items, for example reports and subscriptions, from server to another server. The script supports both SharePoint mode and Native mode
report servers.
Applies to: Reporting Services SharePoint mode | Reporting Services Native mode
In this Topic:
To Download the ssrs_migration.rss Script
Supported Scenarios
Items and resources the script migrates
Required Permissions
How to use the script
Parameter Description
More Examples
Native Mode Report Server to Native Mode Report Server
Native Mode to SharePoint Mode – root site
Native mode to SharePoint Mode –‘bi’ site collection
SharePoint Mode to SharePoint Mode –‘bi’ site collection
Native Mode to Native Mode – Windows Azure Virtual Machine
SharePoint Mode –‘bi’ site collection to a Native Mode Server on Windows Azure Virtual Machine
Verification
Troubleshooting
To Download the ssrs_migration.rss Script
Download the script from the CodePlex site Reporting Services RS.exe script migrates content to a local folder. See the section How to use the script in this
topic for more information.
Supported Scenarios
The script supports both SharePoint mode and Native mode report servers. The script supports the following report server versions:
SQL Server 2016
SQL Server 2014
SQL Server 2012
SQL Server 2008 R2
The script can be used to copy content between report servers of the same mode or different modes. For example, you can run the script to copy
content from a SQL Server 2008 R2 native mode report server to a SQL Server 2012 SP1 SharePoint mode report server. You can run the script from
any server where RS.exe is installed. For example, in the following deployment, you can:
Run RS.exe and the script ON Server A.
To copy content FROM Server B
TO Server C
SERVER NAME
REPORT SERVER MODE
Server A
Native
Server B
SharePoint
Server C
SharePoint
SERVER NAME
REPORT SERVER MODE
For more information on the RS.exe utility, see RS.exe Utility (SSRS).
Items and resources the script migrates
The script will not write over existing content items of the same name. If the script detects items with the same name on the destination server that are on the
source server, the individual items will result in a “failure” message and the script will continue. The following table lists the types of content and resources
the script can migrate to target report server modes.
ITEM
MIGRATED
SHAREPOINT
DESCRIPTION
Passwords
No
No
Passwords are NOT migrated. After
content items are migrated, update the
credential information on the destination
server. For example, data sources with
stored credentials.
My Reports
No
No
The Native mode “My Reports” feature is
based on individual user logins therefore
the scripting service does not have
access to content in “My Reports”
folders for users other than the –u
parameter used to run the rss script.
Also, “My Reports” is not a feature of
Reporting Services SharePoint mode and
items in the folders cannot be copied to
a SharePoint environment. Therefore,
the script does not copy report items
that are in the “My Reports” folders on a
source native mode report server
To migrate the content in “My Reports”
folders with this script, complete the
following:
1. Create new folder(s) in Report
Manager. Optionally, you can create
folders or subfolder for each user.
2. Login as one of the users with “My
Reports” content.
3. In Report Manager, click the My
Reports folder.
4. Click the Details view for the folder.
5. Select each report that you want to
copy.
6. Click Move in the Report Manager
toolbar.
7. Select the desired destination folder.
8. Repeat steps 2-7 for each user.
9. Run the script.
History
No
No
History settings
Yes
Yes
The history settings are migrated
however the history details are NOT
migrated.
Schedules
yes
yes
To migrate schedules, it is required that
SQL Server Agent is running on the
target server. If SQL Server Agent is not
running on the target, you will see an
error message similar to the following:
Migrating schedules: 1 items found. Migrating schedule
theMondaySchedule ... FAILURE: The SQL Agent service i
This operation requires the SQL Agent service. --->
Microsoft.ReportingServices.Diagnostics.Utilities.Sche
Exception: The SQL Agent service is not running. This
the SQL Agent service.
ITEM
MIGRATED
SHAREPOINT
DESCRIPTION
Roles and system policies
Yes
Yes
By default the script will not copy
custom permission schema between
servers. The default behavior is the items
will be coied to the destination server
with the ‘inherit parent permissions’ flag
set to TRUE. If you want the script to
copy permissions for individual items,
use the SECURITY switch.
If the source and target servers are not
the same report server mode, for
example from native mode to SharePoint
mode, and you use the SECURITY switch,
the script will attempt to map default
roles and groups based on the
comparison in the following topic
Compare Roles and Tasks in Reporting
Services to SharePoint Groups and
Permissions. Custom roles and groups
are not copied to the destination server.
When the script is copying between
servers that are the same mode, and
you use the SECURITY switch, the script
will create new roles (native mode) or
groups (SharePoint mode) on the
destination server.
If a role already exists on the destination
sever, the script will create a “Failure”
message similar to the following, and
continue migrating other items. After
the script completes, verify the roles on
the destination server are configured to
meet your needs. the Migrating roles: 8
items found.
Migrating role: Browser ... FAILURE: The role 'Browser
cannot be created. --->
Microsoft.ReportingServices.Diagnostics.Utilities.Role
The role 'Browser' already exists and cannot be create
For more information, see Grant User
Access to a Report Server (Report
Manager)
Note: if a user that exists on the source
server does not exist on the destination
server, the script cannot apply role
assignments on the destination server,
the script cannot apply role assignments,
even if the SECURITY switch is used.
Shared data source
Yes
Yes
The script will not overwrite existing
items on the target server. If an item on
the target server already exists with the
same name, you will see an error
message similar to the following:
Migrating DataSource: /Data Sources/Aworks2012_oltp ..
'/Data Sources/Aworks2012_oltp' already exists. --->
Microsoft.ReportingServices.Diagnostics.Utilities.Item
The item '/Data Source s/Aworks2012_oltp' already exis
Credentials are NOT copied over as part
of the data source. After content items
are migrated, update the credential
information on the destination server.
Shared dataset
Yes
Yes
Folder
Yes
Yes
The script will not overwrite existing
items on the target server. If an item on
the target server already exists with the
same name, you will see an error
message similar to the following:
Migrating Folder: /Reports ... FAILURE: The item '/Rep
-->
Microsoft.ReportingServices.Diagnostics.Utilities.Item
The item '/Reports' already exists.
ITEM
MIGRATED
SHAREPOINT
DESCRIPTION
Report
Yes
Yes
The script will not overwrite existing
items on the target server. If an item on
the target server already exists with the
same name, you will see an error
message similar to the following:
Migrating Report: /Reports/testThe item '/Reports/test
Microsoft.ReportingServices.Diagnostics.Utilities.Item
The item '/Reports/test' already exists.
Parameters
Yes
Yes
Subscriptions
Yes
Yes
History Settings
Yes
Yes
processing options
Yes
Yes
cache refresh options
Yes
Yes
The history settings are migrated
however the history details are NOT
migrated.
Dependent settings are migrated as part
of a catalog item. The following is the
sample out of the script as it migrates a
report (.rdl) and related settings such as
cache refresh options:
- Migrating parameters for report
TitleOnly.rdl 0 items found.
- Migrating subscriptions for report
TitleOnly.rdl: 1 items found.
- Migrating subscription Save in
\\server\public\savedreports as TitleOnly
... SUCCESS
- Migrating history settings for report
TitleOnly.rdl ... SUCCESS
- Migrating processing options for
report TitleOnly.rdl ... 0 items found.
- Migrating cache refresh options for
report TitleOnly.rdl ... SUCCESS
- Migrating cache refresh plans for
report TitleOnly.rdl: 1 items found.
- Migrating cache refresh plan
titleonly_refresh735amM2F ... SUCCESS
Cache refresh plans
Yes
Yes
Images
Yes
Yes
Report parts
Yes
Yes
Required Permissions
The permissions required to read or write items and resources is not the same for all of the methods used in the script. The following table summarizes the
methods used for each item or resource and links to related content. Navigate to the individual topic to see the required permissions. For example the
ListChildren method topic notes the required permissions of:
Native Mode Required Permissions: ReadProperties on Item
SharePoint Mode Required Permissions: ViewListItems
ITEM OR RESOURCE
SOURCE
TARGET
Catalog items
ListChildren
CreateCatalogItem
GetProperties
SetItemDataSources
GetItemDataSources
GetItemReferences
GetItemReferences
CreateDataSource
GetDataSourceContents
CreateLinkedItem
GetItemLink
CreateFolder
ListRoles
CreateRole
Role
GetRoleProperties
ITEM OR RESOURCE
SOURCE
TARGET
System Policy
GetSystemPolicies
SetSystemPolicies
Schedule
ListSchedules
CreateSchedule
Subscription
ListSubscriptions
CreateSubscription
GetSubscriptionProperties
CreateDataDrivenSubscription
GetDataDrivenSubscriptionProperties
Cache refresh plan
ListCacheRefreshPlans
CreateCacheRefreshPlan
GetCacheRefreshPlanProperties
Parameters
GetItemParameters
SetItemParameters
Execution options
GetExecutionOptions
SetExecutionOptions
Cache options
GetCacheOptions
SetCacheOptions
History settings
GetItemHistoryOptions
SetItemHistoryOptions
Item Policy
GetPolicies
SetPolicies
For more information, see Compare Roles and Tasks in Reporting Services to SharePoint Groups and Permissions.
How to use the script
1. Download the script file to a local folder, for example c:\rss\ssrs_migration.rss.
2. Open a command prompt with administrative privileges.
3. Navigate to the folder containing the ssrs_migration.rss file.
4. Run the command with the parameters appropriate for your scenario.
Basic Example, native mode report server to native mode report server:
The following example migrates content from the native mode Sourceserver to the native mode Targetserver.
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\User -p password -v ts="http://TargetServer/reportserver" v tu="Domain\Userser" -v tp="password"
Usage notes:
The script runs in two steps.
The first step is an audit, to return a list of items that will be migrated and the second step is the migration process.
You can cancel the script after step one if you only want to see the possible migration list or you want to modify the parameters. Dependent
settings are not listed in step one. For example, the cache options of a report are not listed but the report itself is.
TIP
If you want to just audit a single server, use the same server for source and destination and cancel after step 1
A good use of the step 1 audit information is to review existing roles on both the source and target Native mode server. The following is an example of
the step one audit list. Notice the list includes a “roles” section because the switch-v security="True" was used:
Retrieve and report the list of items that will be migrated. You can cancel the script after step 1 if you do not want to start the actual
migration.
Retrieving roles:
Role: Browser
Role: Content Manager
Role: Model Item Browser
Retrieve and report the list of items that will be migrated. You can cancel the script after step 1 if you do not want to start the actual
migration.
Retrieving roles:
Role: Browser
Role: Content Manager
Role: CustomRole
Role: Model Item Browser
Role: My Reports
Role: Publisher
Role: Report Builder
Role: System Administrator
Role: System User
Retrieving system policies:
Retrieving system policies:
System policy: BUILTIN\Administrators
System policy: domain\user1
System policy: domain\ueser2
Retrieving schedules:
Schedule: theMondaySchedule
Retrieving catalog items. This may take a while.
Folder: /Data Sources
DataSource: /Data Sources/Aworks2012_oltp
Folder: /images
Resource: /images/Boba Fett.png
Resource: /images/R2-D2.png
Folder: /Reports
Report: /Reports/products
Report: /Reports/test
Report: /Reports/TitleOnly
The SOURCE_URL and TARGET_URL must be valid report server URLs that point to the source and target Reporting Services report server. In native
mode, a report server URL looks like the following:
http://servername/reportserver
In SharePoint mode the URL looks like the following:
http://servername/_vti_bin/reportserver
The virtual folder structure presented to the user in SharePoint might be different than the underlying one. Open
http://servername/_vti_bin/reportserver or http://servername/sites/site_name/_vti_bin/reportserver in a browser to see the non-virtual folder
structure. This is helpful for setting source folder and target folder to something other than "/", for a server in SharePoint mode.
Passwords are not migrated, and must be re-entered, for example data sources with stored credentials.
Parameter Description
PARAMETER
DESCRIPTION
REQUIRED
-s Source_URL
URL of the source report server
Yes
-u Domain\password –p password
Credentials for source server.
OPTIONAL, default credentials are used if missing
-v st="SITE"
OPTIONAL. This parameter is only used for SharePoint
mode report servers.
- v f="SOURCEFOLDER"
Set to "/" for migrating everything, or to something like
"/folder/subfolder" for partial migration. Everything
within this folder will be copied
-v ts="TARGET_URL"
'URL of the target RS server"
-v tu="domain\username" -v tp="password"
'Credentials for target server.
OPTIONAL, default is "/".
OPTIONAL, default credentials are used if missing.
Note: the user will be listed as the “creator” of shared
schedules and “modified by” account for report items, in
the target server.
PARAMETER
DESCRIPTION
-v tst="SITE"
REQUIRED
OPTIONAL. This parameter is only used for SharePoint
mode report servers.
-v tf ="TARGETFOLDER"
'Set to "/" for migrating into the root level. Set to
"/folder/subfolder" to copy into a that already exists.
Everything within "SOURCEFOLDER" will be copied into
"TARGETFOLDER.
OPTIONAL, default is "/".
-v security= "True/False"
If set to “False”, destination catalog items will inherit
security setting according to the settings of the target
system. This is the recommended setting for migrations
between different report server types, for example
native mode to SharePoint mode. If set to “True”, the
script attempts to migrate security settings.
OPTIONAL, default is “False”.
More Examples
Native Mode Report Server to Native Mode Report Server
The following example migrates content from the native mode Sourceserver to the native mode Targetserver.
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\User -p password -v ts="http://TargetServer/reportserver" -v
tu="Domain\Userser" -v tp="password"
The following example adds the security switch:
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\User -p password -v ts="http://TargetServer/reportserver" -v
tu="Domain\Userser" -v tp="password" -v security="True"
Native Mode to SharePoint Mode – root site
The following example migrates content from a native mode SourceServer to the “root site ” on a SharePoint mode server TargetServer. The “Reports” and
“Data Sources” folders on the native mode server as migrated as new libraries on the SharePoint deployment.
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\User -p Password -v
ts="http://TargetServer/_vti_bin/ReportServer" -v tu="Domain\User" -v tp="Password"
Native mode to SharePoint Mode –‘bi’ site collection
The following example migrates content from a native mode server to a SharePoint server that contains a site collection of "sites/bi" and a shared documents
library. The script creates folders in document the destination library. For example, the script will create a “Reports” and "Data Sources” folders in the target
document library.
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\User -p Password -v
ts="http://TargetServer/sites/bi/_vti_bin/reportserver" -v tst="sites/bi" -v tf="Shared Documents" -v tu="Domain\User" -v tp="Password"
SharePoint Mode to SharePoint Mode –‘bi’ site collection
The following example migrates content:
From a SharePoint server SourceServer that contains a site collection of "sites/bi" and a shared documents library.
To a TargetServer SharePoint server that contains a site collection of "sites/bi" and a shared documents library.
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/_vti_bin/reportserver -v st="sites/bi" -v f="Shared Documents" -u Domain\User1 -p
Password -v ts="http://TargetServer/sites/bi/_vti_bin/reportserver" -v tst="sites/bi" -v tf="Shared Documents" -v tu="Domain\User" -v tp="Password"
Native Mode to Native Mode – Windows Azure Virtual Machine
The following example migrates content:
From a Native mode report server SourceServer.
To a TargetServer Native mode report server running on a Windows Azure virtual machine. The TargetServer is not joined to the domain of the
SourceServer and the User2 is an administrator on the Windows Azure virtual machine TargetServer.
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SourceServer/ReportServer -u Domain\user1 -p Password -v
ts="http://ssrsnativeazure.cloudapp.net/ReportServer" -v tu="user2" -v tp="Password2"
TIP
For information on how to use Windows PowerShell to create Reporting Services report servers on Windows Azure virtual machines, see Use PowerShell to Create a
Windows Azure VM With a Native Mode Report Server.
SharePoint Mode –‘bi’ site collection to a Native Mode Server on Windows Azure Virtual
Machine
The following example migrates content:
From a SharePoint mode report server SourceServer that contains a site collection of "sites/bi" and a shared documents library.
To a TargetServer Native mode report server running on a Windows Azure virtual machine. The TargetServer is not joined to the domain of the
SourceServer and the User2 is an administrator on the Windows Azure virtual machine TargetServer.
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://uetesta02/_vti_bin/reportserver -u user1 -p Password -v
ts="http://ssrsnativeazure.cloudapp.net/ReportServer" -v tu="user2" -v tp="Passowrd2"
Verification
The section summarizes some of the steps to take on the destination server to verify content and policies were successfully migrated.
Schedules
To verify schedules on the target server:
Native Mode
1. Browse to Report Manager on the destination server.
2. Click Site Settings on the top menu.
3. Click Schedules in the left pane.
SharePoint Mode:
4. Browse to Site settings.
5. In the Reporting Services group, click Manage Shared Schedules.
Roles and Groups
Native Mode
1. Open SQL Server Management Studio and connect to your native mode report server.
2. In Object Explorer click Security.
3. Click Roles.
Troubleshooting
Use the trace flag –t to receive more information. For example, if you run the script and see a message similar to the following
Could not connect to server: http://<servername>/ReportServer/ReportService2010.asmx
Run the script again with the –t flag, to see a message similar to the following:
System.Exception: Could not connect to server: http://<servername>/ReportServer/ReportService2010.asmx ---> System.Net.WebException: The
request failed with HTTP status 401: Unauthorized. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall) at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at
Microsoft.SqlServer.ReportingServices2010.ReportingService2010.IsSSLRequired() at
Microsoft.ReportingServices.ScriptHost.Management2010Endpoint.PingService(String url, String userName, String password, String domain, Int32
timeout) at Microsoft.ReportingServices.ScriptHost.ScriptHost.DetermineServerUrlSecurity() --- End of inner exception stack trace ---
See Also
RS.exe Utility (SSRS)
Compare Roles and Tasks in Reporting Services to SharePoint Groups and Permissions
Access the Reporting Services WMI Provider
3/24/2017 • 3 min to read • Edit Online
The Reporting Services WMI provider exposes two WMI classes for administration of Native mode report server
instances through scripting:
IMPORTANT
Starting with the SQL Server 2012 release, the WMI provider is supported for only native mode report servers. SharePoint
mode report servers can be managed with SharePoint Central Administration pages and PowerShell scripts.
CLASS
NAMESPACE
DESCRIPTION
MSReportServer_Instance
root\Microsoft\SqlServer\ReportServer\
RS_<EncodedInstanceName>\v13
Provides basic information required for
a client to connect to an installed report
server.
MSReportServer_ConfigurationSetting
root\Microsoft\SqlServer\ReportServer\
RS_<EncodedInstanceName>\v13\Adm
in
Represents the installation and runtime parameters of a report server
instance. These parameters are stored
in the configuration file for the report
server.
** Important *\* This class is only
accessible with administrative privileges.
An instance of each of the above classes is created for each report server instance. You can use any Microsoft or
third party tools to access the WMI objects exposed by the report server, including WMI programming interfaces
exposed by the .NET Framework itself. This topic describes how to access and use the WMI class instances with the
PowerShell command Get-WmiObject.
Determine the Instance Name in the Namespace String
The instance name in the namespace path for the Reporting Services WMI classes is an encoding of the instance
names that you specify when installing the named Reporting Services instances. Namely, special characters in the
instance names are encoded. For example, an underline (_) is encoded as “_5f”, so an instance name of
“My_Instance” is encoded as “My_5fInstance” in the WMI namespace path.
To list the encoded instance names of your report server instances in the WMI namespace path, use the following
PowerShell command:
PS C:\windows\system32> Get-WmiObject –namespace root\Microsoft\SqlServer\ReportServer –class __Namespace –
ComputerName hostname | select Name
Access the WMI Classes Using PowerShell
To access the WMI classes, run the following command:
PS C:\windows\system32> Get-WmiObject –namespace <namespacename> –class <classname> –ComputerName <hostname>
For example, to access the MSReportServer_ConfigurationSetting class on the default report server instance of the
host myrshost, run the following command. The default report server instance must be installed on myrshost for
this command to succeed.
PS C:\windows\system32> Get-WmiObject –namespace
"root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERER\v11\Admin" -class MSReportServer_ConfigurationSetting ComputerName myrshost
This command syntax outputs all class property names and values. Note that all instances of the class
MSReportServer_ConfigurationSetting is returned, even though you are accessing the class in the namespace of
the default report server instance (RS_MSSQLSERVER). For example, if myrshost is installed with the default report
server instance and a named report server instance called SHAREPOINT, this command will return two WMI
objects and output the property names and values for both report server instances.
To return a specific class instance when multiple instances are returned, use the –Filter parameter to filter the
results based on properties with unique values such as InstanceName. For example, to return only the WMI object
for the default report server instance, use the following command:
PS C:\windows\system32> Get-WmiObject -namespace
"root\Microsoft\SqlServer\ReportServer\RS_MSSQLServer\v13\Admin" -class MSReportServer_ConfigurationSetting ComputerName myrshost -filter "InstanceName='MSSQLSERVER'"
Query the Available Methods and Properties
To see what methods and properties are available in one of the Reporting Services WMI classes, pipe the results
from Get-WmiObject to the Get-Member command. For example:
PS C:\windows\system32> Get-WmiObject -namespace
"root\Microsoft\SqlServer\ReportServer\RS_MSSQLServer\v13\Admin" -class MSReportServer_ConfigurationSetting ComputerName myrshost | Get-Member
Use a WMI Method or Property
Once you have the WMI objects to the Reporting Services classes and know the available methods and properties,
you can use these methods and properties. For example, if you have a named report server instance in SharePoint
integrated mode called SHAREPOINT, use the following command sequence to retrieve the URL for the SharePoint
Central Administration site:
PS C:\windows\system32> $rsconfig = Get-WmiObject -namespace
"root\Microsoft\SqlServer\ReportServer\RS_MSSQLServer\v13\Admin" -class MSReportServer_ConfigurationSetting ComputerName myrshost -filter "InstanceName='SHAREPOINT'"
PS C:\windows\system32> $rsconfig.GetAdminSiteUrl()
See Also
Reporting Services WMI Provider Library Reference (SSRS)
RsReportServer.config Configuration File
Report Server Command Prompt Utilities (SSRS)
3/24/2017 • 1 min to read • Edit Online
SQL Server Reporting Services includes several command line utilities that you can use to administer a report
server. These utilities are installed automatically when you install a report server.
NAME
COMMAND FILE
RSS utility
rs.exe
Powershell cmdlets
Rsconfig utility
rsconfig.exe
SUPPORTED DEPLOYMENT
MODE
DESCRIPTION
Native mode and SharePoint
mode. The SQL Server 2008
R2 release introduced
SharePoint mode support.
The rs utility is a script host
that you can use to perform
scripted operations. Use this
tool to run Microsoft Visual
Basic scripts that copy data
between report server
databases, publish reports,
create items in a report
server database, and more.
To learn more about using
scripts to administer a
server, see Script
Deployment and
Administrative Tasks.
SharePoint only
For a list of the of the
powershell cmdlets, see
PowerShell cmdlets for
Reporting Services
SharePoint Mode.
Native only
The rsconfig utility is used to
configure and manage a
report server connection to
the report server database.
You can also use it to
specify a user account to
use for unattended report
processing. For more
information, see Reporting
Services Report Server
(Native Mode). To learn
more about connection
configuration, see Configure
a Report Server Database
Connection (SSRS
Configuration Manager).
NAME
COMMAND FILE
SUPPORTED DEPLOYMENT
MODE
Rskeymgmt Utility
rskeymgmt.exe
Native only
DESCRIPTION
The rskeymgmt utility is an
encryption key management
tool. You can use it to back
up, apply, recreate, and
delete symmetric keys. You
can also use this tool to
attach a report server
instance to a shared report
server database. Rskeymgmt
can be used in database
recovery operations. You
can reuse an existing
database in a new
installation by applying a
back up copy of the
symmetric key. If the keys
cannot be recovered, this
tool provides a way to
delete encrypted content
that you no longer use. To
learn more about key
management and storage of
sensitive data, see Store
Encrypted Report Server
Data (SSRS Configuration
Manager) and Configure
and Manage Encryption
Keys (SSRS Configuration
Manager).
NOTE
If you prefer to use a tool that has a graphical user interface, you can use the Reporting Services Configuration manager
instead of rsconfig and rskeymgmt.
See Also
Reporting Services Configuration Manager (Native Mode)
Reporting Services Tools
Reporting Services Report Server (Native Mode)
rskeymgmt Utility (SSRS)
3/24/2017 • 7 min to read • Edit Online
Extracts, restores, creates, and deletes the symmetric key used to protect sensitive report server data against
unauthorized access. This utility is also used to join report server instances in a scale-out deployment. A report
server scale-out deployment refers to multiple report server instances that share a single report server database.
Syntax
rskeymgmt {-?}
{–eextract}
{–aapply}
{-ddeleteall}
{–srecreatekey}
{–rremoveinstancekey}
{-jjoinfarm}
{-iinstance}
{-ffile}
{-pencryptionpassword}
{-mremotecomputer}
{-ninstancenameofremotecomputer}
{-uadministratoruseraccount}
{-vadministratorpassword}
{-ttrace}
Arguments
-?
Displays the syntax of rskeymgmt arguments.
-e
Extracts the symmetric key used to encrypt and decrypt data for the report server instance so that you can copy it
to a file.
This argument does not take a value. However, you must include additional arguments on the command line to
complete the extraction. The arguments that you must specify include -f and-p.
-a
Replaces an existing symmetric key with a copy that you provide in a password protected backup file. All instances
of the symmetric key are updated.
This argument does not take a value. However, you must include additional arguments on the command line to
select the file that contains the key to be applied. The arguments that you can specify include -f and-p.
-d
Deletes all symmetric key instances and all encrypted data in a report server database. This argument does not take
a value.
-s
Generates a new symmetric key and re-encrypts all encrypted content using the new key. All instances of the
symmetric key are regenerated.
-j
Configures a remote report server instance to share the report server database that is used by the local report
server instance.
-r installationID
Removes the symmetric key information for a specific report server instance, thereby removing the report server
from a scale-out deployment. The installationID is a GUID value that can be found in the RSReportserver.config file.
-f file
Specifies a fully qualified path to the file that stores a backup copy of the symmetric keys.
For rskeymgmt -e, the symmetric key is written to the file you specify.
For rskeymgmt -a, the symmetric key value stored in the file is applied to the report server instance.
-p password
(Required for -f) Specifies the password used to back up or apply a symmetric key. This value cannot be empty.
-i
Specifies a local report server instance. This argument is optional if you installed the report server on the default
SQL Server instance (the default value for -i is MSSQLSERVER). If you installed the report server as a named
instance, -i is required.
-m
Specifies the name of the remote computer that hosts the report server instance you are joining to the report
server scale-out deployment. Use the name of the computer that identifies it on your network.
-n
Specifies the name of the report server instance on a remote computer. This argument is optional if you installed
the report server on the default SQL Server instance (the default value for -n is MSSQLSERVER). If you installed the
report server as a named instance, -n is required.
-u useraccount
Specifies the administrator account on the remote computer that you are joining to the scale-out deployment. If an
account is not specified, the credentials of the current user are used.
-v password
(Required for -u) Specifies the password of an administrator account on the remote computer that you want to join
to the scale-out deployment.
-t trace
Outputs error messages to the trace log. This argument does not take a value. For more information, see Report
Server Service Trace Log.
Permissions
You must be a local administrator to run the tool, and you must run it locally on the computer that hosts the report
server. The rskeymgmt utility works with the local Report Server Windows instance (the utility cannot connect to
remote instances of the Report Server Windows service so it cannot be used to manage the encryption keys of a
remote report server instance).
NOTE
If you are using the -u and -v arguments, be sure to specify an account that has administrator permissions on the remote
computer.
Examples
The following examples illustrate ways of using rskeymgmt. The following examples show how to extract, restore,
and delete encryption keys, and how to configure a report server scale-out deployment.
Extracting Encryption Keys
This example shows how to create a backup copy of the encryption key and save it to a password-protected file on
a floppy disk. If the report server is installed as a named instance, add the -i argument.
rskeymgmt -e -f a:\backupkey\keys -p <password>
Restoring Encryption Keys
This example shows how to replace the encryption key. You must specify the location of the backup copy of the key
and the password that unlocks the file.
rskeymgmt -a -f a:\backupkey\keys -p <password>
Deleting Encryption Keys and Encrypted Content
This example shows how to delete all encryption keys stored in a report server. If your installation is a report server
scale-out deployment, the encryption keys for all report server instances that are included in the deployment will
be deleted. Deleting an encryption key also deletes any existing encrypted values in the report server database. For
more information about encrypted content, see Store Encrypted Report Server Data (SSRS Configuration
Manager).
rskeymgmt -d
Joining a Remote Report Server Named Instance to a Scale-out Deployment
This example shows how to add a report server instance that is installed on a remote computer to a report server
scale-out deployment. You must run the command on one of the computers that is already configured to use the
shared database. The command arguments specify the remote report server instance you want to join to the scaleout deployment.
rskeymgmt -j -m <remotecomputer> -n <namedreportserverinstance> -u <administratoraccount> -v
<administratorpassword>
NOTE
A report server scale-out deployment refers to a deployment model where multiple report server instances share the same
report server database. A report server database can be used by any report server instance that stores its symmetric keys in
the database. For example, if a report server database contains key information for three report server instances, all three
instances are considered to members of the same scale-out deployment.
Joining Report Server Instances on the Same Computer
You can create a scale-out deployment from multiple report server instances that are installed on the same
computer. Do not set the -u and -v arguments if you are joining report server instances that are installed locally.
The -u and -v arguments are used only when you are joining an instance from a remote computer. If you specify
the arguments, you will get the following error: "User credentials cannot be used for local connections."
The following example illustrates the syntax for creating a scale-out deployment using multiple local instances. In
this example, <initializedinstance> is the name of an instance that is already initialized to use the report server
database, and <newinstance> is the name of the instance that you want to add to the deployment:
rskeymgmt -j -i <initializedinstance> -m <computer name> -n <newinstance>
Removing Encryption Keys for a Single Report Server in a Scale-out Deployment
This example shows how to remove the encryption keys for a single report server in a report server scale-out
deployment. The keys are removed from the report server database. Once the keys for that report server instance
are removed, that report server instance can no longer access encrypted data in the database, effectively removing
it from the scale-out deployment.
Removing a report server instance from a scale-out deployment requires you to specify an installation ID. The
installation ID is a GUID stored in the RSReportserver.config file of the report server instance for which you want to
remove encryption keys. You must run the following command on the computer that you want to remove from the
scale-out deployment. If the report server is installed as a named instance, use the -i argument to specify the
instance. For more information, see RsReportServer.config Configuration File.
rskeymgmt -r <installationID>
File Location
Rskeymgmt.exe is located at <drive>:\Program Files\Microsoft SQL Server\110\Tools\Binn or at
<drive>:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn. You can run the utility from any folder
on your file system.
Remarks
A report server encrypts stored credentials and connection information. A public key and a symmetric key are used
to encrypt data. A report server database must have valid keys in order for the report server to run. You can use
rskeymgmt to back up, delete, or restore the keys. If the keys cannot be restored, this tool provides a way to delete
encrypted content that can no longer be used.
The rskeymgmt utility is used to manage the key set that is defined during Setup or during initialization. It
connects to the local Report Server Windows service through a Remote Procedure Call (RPC) endpoint. The Report
Server Windows service must be running in order for this utility to work.
For more information about the encryption keys, see Configure and Manage Encryption Keys (SSRS Configuration
Manager) and Initialize a Report Server (SSRS Configuration Manager).
See Also
Scale-out Deployment - Reporting Services Native mode (Configuration Manager)
Reporting Services Report Server (Native Mode)
Report Server Command Prompt Utilities (SSRS)
Configure and Manage Encryption Keys (SSRS Configuration Manager)
rsconfig Utility (SSRS)
3/24/2017 • 5 min to read • Edit Online
The rsconfig.exe utility encrypts and stores connection and account values in the RSReportServer.config file.
Encrypted values include report server database connection information and account values used for unattended
report processing.
Syntax
rsconfig {-?}
{–cconnection}
{–eunattendedaccount}
{–mcomputername}
{–iinstancename}
{–sservername}
{–ddatabasename}
{–aauthmethod}
{-uusername}
{-ppassword}
{-ttrace}
Arguments
TERM
OPTIONAL/REQUIRED
DEFINITION
-?
Optional.
Displays the syntax of Rsconfig.exe
arguments.
-c
Required if -e argument is not used.
Specifies the connection string,
credentials, and data source values used
to connect a report server to the report
server database.
This argument does not take a value.
However, additional arguments must be
specified with it to provide all of the
required connection values.
Arguments that you can specify with -c
include -m, -s, -i,-d,-a,-u,-p, and-t.
-e
Required if -c argument is not used.
Specifies the unattended report
execution account.
This argument does not take a value.
However, you must include additional
arguments on the command line to
specify that values that are encrypted in
the configuration file.
Arguments that you can specify with -e
include -u and -p. You can also set -t.
TERM
OPTIONAL/REQUIRED
DEFINITION
-m computername
Required if you are configuring a
remote report server instance.
Specifies the name of the computer that
is hosting the report server. If this
argument is omitted, the default is
localhost.
-s servername
Required.
Specifies the SQL Server instance that
hosts the report server database.
-i instancename
Required if you are using named
instances.
If you used a named SQL Server
instance to host the report server
database, this value specifies the named
instance.
-d databasename
Required.
Specifies the name of the report server
database.
-a authmethod
Required.
Specifies the authentication method
that the report server uses to connect
to the report server database. Valid
values are Windows or SQL (this
argument is not case-sensitive).
Windows specifies that the report
server use Windows Authentication.
SQL specifies that the report server use
SQL Server Authentication.
-u [domain\]username
Required with -e Optional with -c.
Specifies a user account for the report
server database connection or for the
unattended account.
For rsconfig -e, this argument is
required. It must be a domain user
account.
For rsconfig -c and -a SQL, this
argument must specify a SQL Server
login.
For rsconfig -c and -a Windows, this
argument may specify a domain user, a
built-in account, or service account
credentials. If you are specifying a
domain account, specify domain and
username in the format
domain\username. If you are using a
built-in account, this argument is
optional. If you want to use service
account credentials, omit this argument.
-p password
Required if -u is specified.
Specifies the password to use with the
username argument. You can set this
argument to a blank value if the
account does not require a password.
This value is case-sensitive for domain
accounts.
TERM
OPTIONAL/REQUIRED
DEFINITION
-t
Optional.
Outputs error messages to the trace
log. This argument does not take a
value. For more information, see Report
Server Service Trace Log.
Permissions
You must be a local administrator on the computer that hosts the report server you are configuring.
File Location
Rsconfig.exe is located in \Program Files\Microsoft SQL Server\110\Tools\Binn. You can run the utility from
any folder on your file system.
Remarks
Rsconfig.exe is used for two purposes:
To modify the connection information that a report server uses to connect to a report server database.
To configure a special account that the report server uses to log on to a remote database server when other
credentials are not available.
You can run thersconfig utility on a local or remote instance of Reporting Services. You cannot use the
rsconfig utility to decrypt and view values that are already set.
Before you can run this utility, Windows Management Instrumentation (WMI) must be installed on the
computer that you are configuring.
Examples
The following examples illustrate ways of using rsconfig.
Specifying a Domain User Account
This example shows how to configure a report server to use a domain user account when connecting to a local
report server database.
rsconfig -c -s <SQLSERVERNAME> -d reportserver -a Windows -u <MYDOMAIN\MYACCOUNT> -p <PASSWORD>
Specifying a SQL Server Database User Account
This example shows how to configure a report server to use SQL Server login to connect to a remote report server
database.
rsconfig -c -m <REMOTECOMPUTERNAME> -s <SQLSERVERNAME> -d reportserver -a SQL -u SA -p <SAPASSWORD>
Specifying a Built-in Account
This example shows how to configure a report server to use a built-in account when connecting to a local report
server database. Notice that -u is not used. Examples of supported built-in account values include NT
AUTHORITY\SYSTEM for Local System and NT AUTHORITY\NETWORKSERVICE for Network Service ( Microsoft
Windows Server 2003 only).
rsconfig -c -s <SQLSERVERNAME> -d reportserver -a Windows "NT AUTHORITY\SYSTEM"
Specifying a Service Account
This example shows how to configure a report server to use the Report Server Windows service account and Web
service account when connecting to a local report server database. Notice that -u is not used and that no account
information is specified. When you eliminate account values from the command, the rsconfig utility uses
integrated security and the service account that each service runs under.
rsconfig -c -s <SQLSERVERNAME> -d reportserver -a Windows
Specifying the Unattended Account on a Local Server
This example shows how to configure the account used for unattended report execution for reports that do not
pass credentials to the external data source. The account must be a Windows domain account. You cannot specify a
SQL Server login for the user name and password. The account is configured on a local report server instance.
Error messages are captured in the trace logs in the ReportingServices\LogFiles folder.
rsconfig -e -u <DOMAIN\ACCOUNT> -p <PASSWORD> -t
Specifying the Unattended Account on a Remote Server
This example shows how to configure the account on a remote report server instance that is the same version as
Rsconfig.exe (for example, the report server and Rsconfig.exe are the SQL Server 2008 R2 version). Error message
information is captured in the trace logs on the remote server.
rsconfig -e -m <REMOTECOMPUTERNAME> -s <SQLSERVERNAME> -u <DOMAIN\ACCOUNT> -p <PASSWORD> -t
See Also
Configure a Report Server Database Connection (SSRS Configuration Manager)
Configure the Unattended Execution Account (SSRS Configuration Manager)
Reporting Services Report Server (Native Mode)
Store Encrypted Report Server Data (SSRS Configuration Manager)
Reporting Services Configuration Files
Report Server Command Prompt Utilities (SSRS)
RsReportServer.config Configuration File
RS.exe Utility (SSRS)
5/24/2017 • 4 min to read • Edit Online
The rs.exe utility processes script that you provide in an input file. Use this utility to automate report server
deployment and administration tasks.
NOTE
Beginning with SQL Server 2008 R2, the rs utility is supported against report servers that are configured for SharePoint
integrated mode as well as servers configured in native mode. Previous versions only supported native mode
configurations.
Syntax
rs {-?}
{-i input_file=}
{-s serverURL}
{-u username}
{-p password}
{-e endpoint}
{-l time_out}
{-b batchmode}
{-v globalvars=}
{-t trace}
File Location
RS.exe is located at \Program Files\Microsoft SQL Server\110\Tools\Binn. You can run the utility from any
folder on your file system.
Arguments
-?
(Optional) Displays the syntax of rs arguments.
-i input_file
(Required) Specifies the .rss file to execute. This value can be a relative or fully qualified path to the .rss file.
-s serverURL
(Required) Specifies the Web server name and report server virtual directory name to execute the file against. An
example of a report server URL is http://examplewebserver/reportserver . The prefix http:// or https:// at the
beginning of the server name is optional. If you omit the prefix, the report server script host tries to use https
first, and then uses http if https does not work.
-u [domain\]username
(Optional) Specifies a user account used to connect to the report server. If -u and -p are omitted, the current
Windows user account is used.
-p password
(Required if -u is specified) Specifies the password to use with the -u argument. This value is case-sensitive.
-e
(Optional) Specifies the SOAP endpoint against which the script should run. Valid values are the following:
Mgmt2010
Mgmt2006
Mgmt2005
Exec2005
If a value is not specified, the Mgmt2005 endpoint is used. For more information about the SOAP
endpoints, see Report Server Web Service Endpoints.
-l time_out
(Optional) Specifies the number of seconds that elapse before the connection to the server times out. The
default is 60 seconds. If you do not specify a time-out value, the default is used. A value of 0 specifies that
the connection never times out.
-b
(Optional) Specifies that the commands in the script file run in a batch. If any commands fail, the batch is
rolled back. Some commands cannot be batched, and those run as usual. Only exceptions that are thrown
and are not handled within the script result in a rollback. If the script handles an exception and returns
normally from Main, the batch is committed. If you omit this parameter, the commands run without
creating a batch. For more information, see Batching Methods.
-v globalvar
(Optional) Specifies global variables that are used in the script. If the script uses global variables, you must
specify this argument. The value that you specify must be valid for global variable defined in the .rss file.
You must specify one global variable for each –v argument.
The -v argument is specified on the command line and is used to set the value for a global variable that is
defined in your script at run time. For example, if your script contains a variable named parentFolder, you
can specify a name for that folder on the command line:
rs.exe -i myScriptFile.rss -s http://myServer/reportserver -v parentFolder="Financial Reports"
Global variables are created with the names given and set to the values supplied. For example, -v a="1" -v
b="2" results in a variable named a with a value of"1" and a variable b with a value of "2".
Global variables are available to any function in the script. A backslash and quotation mark (\") is
interpreted as a double quotation mark. The quotation marks are required only if the string contains a
space. Variable names must be valid for Microsoft Visual Basic; they must start with alphabetical character
or underscore and contain alphabetical characters, digits, or underscores. Reserved words cannot be used
as variable names. For more information about using global variables, see Built-in Collections in
Expressions (Report Builder and SSRS).
-t
(Optional) Outputs error messages to the trace log. This argument does not take a value. For more
information, see Report Server Service Trace Log.
Permissions
To run the tool, you must have permission to connect to the report server instance you are running the script
against. You can run scripts to make changes to the local computer or a remote computer. To make changes to a
report server installed on a remote computer, specify the remote computer in the -s argument.
Examples
The following example illustrates how to specify the script file that contains Visual Basic .NET script and Web
service methods that you want to execute.
rs –i c:\scriptfiles\script_copycontent.rss -s http://localhost/reportserver
For a detailed example, see Sample Reporting Services rs.exe Script to Copy Content between Report Servers.
For additional examples, see Run a Reporting Services Script File
Remarks
You can define scripts to set system properties, publish reports, and so forth. The scripts that you create can
include any methods of the Reporting Services API. For more information about the methods and properties
available to you, see Report Server Web Service.
The script must be written in Visual Basic .NET code, and stored in a Unicode or UTF-8 text file with an .rss file
name extension. You cannot debug scripts with the rs utility. To debug a script, run the code within Microsoft
Visual Studio.
TIP
For a detailed example, see Sample Reporting Services rs.exe Script to Copy Content between Report Servers.
See Also
Run a Reporting Services Script File
Script Deployment and Administrative Tasks
Script with the rs.exe Utility and the Web Service
Report Server Command Prompt Utilities (SSRS)
Tutorial: How to Locate and Start Reporting Services
Tools (SSRS)
5/30/2017 • 6 min to read • Edit Online
This tutorial introduces the tools used to configure a report server, manage report server content and operations,
and create and publish paginated and mobile Reporting Services reports. If you are already familiar with the tools,
you can move on to other tutorials to learn skills for using Reporting Services. For other tutorials, see Reporting
Services Tutorials (SSRS).
Reporting Services Configuration Manager (Native Mode)
Use the Native mode configuration manager to complete the following:
Specify the service account.
Create or upgrade the report server database.
Modify the connection properties.
Specify URLs.
Manage encryption keys.
Configure unattended report processing and e-mail report delivery.
Installation: Reporting Services Configuration Manager is installed when you install Reporting Services
Native mode. For more information, see Install Reporting Services Native Mode Report Server.
To start the Reporting Services Configuration Manager
1. On the Windows start screen, type reporting and in the Apps search results, click Reporting Services
Configuration Manager.
Or
Click Start, then click Programs, then click Microsoft SQL Server 2017, then click Configuration Tools,
and then click Reporting Services Configuration Manager.
The Report Server Installation Instance Selection dialog box appears so that you can select the report
server instance you want to configure.
2. In Server Name, specify the name of the computer on which the report server instance is installed. The
name of the local computer is specified by default, but you can also type the name of a remote SQL Server
instance.
If you specify a remote computer, click Find to establish a connection. The report server must be configured
for remote administration in advance. For more information, see Configure a Report Server for Remote
Administration.
3. In Instance Name, choose the SQL Server Reporting Services instance that you want to configure. Only
SQL Server 2008 and later report server instances appear in the list. You cannot configure earlier versions of
Reporting Services.
4. Click Connect.
5. To verify that you launched the tool, compare your results to the following image:
Next Steps: Configure and Administer a Report Server (SSRS Native Mode) and Reporting Services
Configuration Manager (Native Mode).
Web Portal (Native Mode)
Use Web portal (SSRS Native Mode) to set permissions, manage subscriptions and schedules, and work with
reports. You can also use the Web Portal to view reports.
Installation: The Web Portal Is installed when you install Reporting Services Native mode: Install Reporting
Services Native Mode Report Server
Before you can open the Web Portal, you must have sufficient permissions (initially, only members of the local
Administrators group have permissions that provide access to the Web Portal features). The Web Portal provides
different pages and options depending on the role assignments of the current user. Users who have no
permissions will get an empty page. Users with permissions to view reports will get links that they can click to open
the reports. To learn more about permissions, see Roles and Permissions (Reporting Services).
To start The Web Portal
1. Open your browser. For information on supported browsers and browser versions, see Browser Support for
Reporting Services and Power View.
2. In the address bar of the Web browser, type the Web Portal URL. By default, the URL is
http://<serverName>/reports . You can use the Reporting Services Configuration tool to confirm the server
name and URL. For more information about URLs used in Reporting Services, see Configure Report Server
URLs (SSRS Configuration Manager).
3. The Web Portal opens in the browser window. The startup page is the Home folder. Depending on
permissions, you might see additional folders, hyperlinks to reports, and resource files within the startup
page. You might also see additional buttons and commands on the toolbar.
4. If you run the Web Portal on the local report server, see Configure a Native Mode Report Server for Local
Administration (SSRS).
Management Studio
Report server administrators can use Management Studio to manage a report server alongside other SQL Server
component servers. For more information, see Use SQL Server Management Studio.
To Start SQL Server Management Studio
1. From the Windows Start Screen type sql server and in the Apps search results, click SQL Server
Management Studio.
Or
Click Start, then click All Programs, then click Microsoft SQL Server 2017, and then click SQL Server
Management Studio. The Connect to Server dialog box appears.
2. If the Connect to Server dialog box does not appear, in Object Explorer, click Connect and then select
Reporting Services.
3. In the Server type list, select Reporting Services. If Reporting Services is not on the list, it is not installed.
4. In the Server name list, select a report server instance. Local instances appear in the list. You can also type
the name of a remote SQL Server instance.
5. Click Connect. You can expand the root node to set server properties, modify role definitions, or turn off
report server features.
SQL Server Data Tools with Report Designer and Report Wizard
You have a choice of two different tools for creating SQL Server paginated reports: Report Designer and Report
Builder.
Report Designer is available in SQL Server Data Tools (SSDT) - Visual Studio. The Report Designer design surface
includes tabbed windows, wizards, and menus used to access report authoring features. The report designer tool
becomes available when you choose a Report Server Project or a Report Server Wizard template in SQL Server
Data Tools (SSDT). To learn more, see Reporting Services in SQL Server Data Tools (SSDT).
Download SQL Server Data Tools.
To start Report Designer
1. Open SQL Server Data Tools.
2. On the File menu, point to New, and then click Project.
3. In the Project Types list, click Business Intelligence Projects.
4. In the Templates list, click Report Server Project. The following diagram shows how the project templates
appear in the dialog box:
5. Type a name and location for the project, or click Browse and select a location.
6. Click OK. SQL Server Data Tools (SSDT) opens with the Visual Studio start page. Solution Explorer provides
categories for creating reports and data sources. You can use these categories to create new reports and
data sources. Tabbed windows appear when you create a report definition. The tabbed windows are Data,
Layout, and Preview..
To get started on your first report, see Create a Basic Table Report (SSRS Tutorial). To learn more about
query designers you can use within Report Designer, see Query Design Tools (SSRS).
Report Builder
Report Builder in SQL Server 2016 is a stand-alone application you can use to create paginated reports outside
SQL Server. You can customize and update all existing reports, regardless of whether they were created in Report
Designer or in previous versions of Report Builder. You can install it from the SQL Server web portal or from the
Microsoft Download Center.
Download Report Builder from the Microsoft Download Center.
To start Report Builder
1. In the SQL Server web portal, on the New menu, select Paginated Report.
2. If Report Builder isn't installed on this computer yet, select Get Report Builder.
Or
Download Report Builder from the Microsoft Download Center.
3. Report Builder opens and you can create or open a paginated report.
SQL Server Mobile Report Publisher
Use SQL Server Mobile Report Publisher to create mobile reports you can view in the SQL Server web portal and in
mobile devices such as iPads and iPhones. You can install it from the SQL Server web portal or from the Microsoft
Download Center.
Download SQL Server Mobile Report Publisher from the Microsoft Download Center.
To start Mobile Report Publisher
1. In the SQL Server web portal, on the New menu, select Mobile Report.
2. If Mobile Report Publisher isn't installed on this computer yet, select Get Mobile Report Publisher.
Or
Download SQL Server Mobile Report Publisher from the Microsoft Download Center.
3. Mobile Report Publisher opens and you can create or open a mobile report.
Next steps
Download SQL Server Mobile Report Publisher
Download Report Builder
Download SQL Server Data Tools Install Reporting Services SharePoint Mode
Reporting Services Report Server
Query Design Tools
Reporting Services Tutorials
More questions? Try asking the Reporting Services forum
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising