In Reporting Services, reports, report models, and data-driven subscriptions retrieve data from external data sources. To connect to an external data source, a report server uses data source connection information that is defined in or referenced from the report, model, or subscription. Data source connection properties are always defined with the report or model when you create it, but can be independently managed after the report or model is published to a report server.
To manage report data sources, you can use Report Manager for a native mode report server or application pages on a SharePoint site if you deployed the report server in SharePoint integrated mode.
Managing data source connections are characterized by the following tasks, which are described in this topic:
Changing connection strings.
Creating and using shared data sources on a report server, including switching an embedded data source for a shared data source.
Controlling access to data source properties by setting permissions on the report, model, or any shared data sources you are using.
Notice that modifying queries is not part of data source connection management. To modify a query for a report or model, you must use an authoring tool and make your changes in the report or model definition.
Data source properties that you can manage on a report server are:
How to manage it
Data source type
Determines which report server data processing extension to use on the external data. Examples of data processors include SQL Server, Analysis Services, and Oracle.
The data source type is a managed property because it is configurable. However, you should only configure a data source type if you are creating a new shared data source.
Do not change the data source type in the property pages of a published report or model, as doing so will almost certainly invalidate the connection. It is unlikely that the data structures required by a report or model will be identical on a different data platform.
Establishes the initial connection to an external data source. A report can use static or dynamic connection strings.
A static connection string is a set of values that the report always uses to connect to the same data source each time the report runs.
A dynamic connection string is an expression that you build into the report, allowing the user to select which data source to use at run time. You must build the expression and data source selection list into the report when you create it in Report Designer.
Changing a connection string is useful if you move a data source to another computer, or if you created reports using test data but you want to deploy the reports with a production database.
You can manage a static connection string by replacing the original string with a different one.
To manage a dynamic connection string in Report Manager or on a SharePoint site, you are limited to replacing it with a static one. You cannot edit the expression itself, nor change the data source selection list. To change the expression or valid values list, you must edit the report definition and republish it to the report server. For more information, see Data Connections, Data Sources, and Connection Strings (SSRS).
Provides the name and password of a user who has permission to read data from the data source.
If a data source does not support authentication (for example, if the data source is an XML file on the file system), you can configure the unattended execution account to allow the report server to connect to the external data source without passing credentials.
You can manage credentials by updating the user account or a password if it expired.
You can also change the way credentials are obtained (for example, prompting users to enter credentials at run time).
If you want to users to be able to subscribe to a report, you must configure the report to use stored credentials.
If you publish a report with data source properties embedded in the report, consider switching to shared data source properties. Shared data sources are easier to manage because you can update credentials and connection strings in one page. All reports, models, and data-driven subscriptions that use that data source pick up the changes immediately. You can also take a shared data source offline, effectively pausing the report or subscription to prevent it from executing while you troubleshoot or investigate any problems that arise.
By default, anyone who has permission to manage reports can set any property on the report, including properties that determine the data source type, connection string, credentials, and whether the report gets connection information from an embedded or a shared data source. For more information about which tasks and permissions control access to data source properties on a native mode report server, see Secure Shared Data Source Items and Secure Reports and Resources.
Permissions to view and edit properties for items in a SharePoint library are determined by the site administrator. For more information about which permissions control access to data source connection properties, see SharePoint Site and List Permission Reference for Report Server Items.
You can use a variety of tools to create and modify data source properties. The following table summarizes the approaches and tools, and provides a link to additional instructions.
View examples of connection strings.
Choose an approach for getting credentials to connect to a data source.
Add data source connection properties to a report definition (.rdl) file.
Add and link to a shared data source (.rds) file in report project.
Create a predefined list of data sources that users can select at run time. When a user requests a report, the report provides a list of data sources. The user must select which data source to use prior to running the report. To add a data source selection list to a report, you use an expression.
This is known as a dynamic data source connection.
Create a shared data source item on a report server.
Store credentials as a prerequisite for creating subscriptions or report snapshots.
Edit data source connection properties on a published report.
Create a shared data source item on a report server.
Use existing .odc connection information with a report.
Managing data source connections to report data sources is not the same as managing the report server connection to the report server database. For more information about a report server connection to its internal data store, see Configure a Report Server Database Connection (SSRS Configuration Manager).