Data Sources Properties Page (Report Manager)

Use the Data Sources properties page to define how the current report connects to an external data source. You can override the data source connection information that was originally published with the report. If multiple data sources are used with a report, each data source has its own section in the properties page. Data sources are listed in the order in which they are defined in the report.

When specifying a data source to use with the report, you can use a shared data source that is created and managed separately from the reports that use it. If you do not want to use a shared data source item, you can define a data source connection to use with the report.

To open this page, select a report, click the Properties tab at the top of the page, and then click the Data Sources tab at the side of the page.

A shared data source

Specify a shared data source to use with the report. For more information about creating a new data source, see How to: Create, Delete, or Modify a Shared Data Source (Report Manager).


Click Browse to open the Data Source Selection page, which is used to select a shared data source. For more information, see Data Source Selection Page (Report Manager).

A custom data source

Specify how the report connects to the data source.

The following options are used to specify a custom data source connection.

Connection Type

Specify the data processing extension that is used to process data from the data source. The report server includes data processing extensions for SQL Server, Analysis Services, Oracle, XML, SQL Server Integration Services, SAP, OLE DB, and ODBC. Additional data processing extensions may be available from third-party vendors.

Note that if you are using SQL Server Express with Advanced Services, you can only use local SQL Server data sources. For more information, see Reporting Services in SQL Server Express with Advanced Services.

Connection String

Specify the connection string that the report server uses to connect to the data source. The connection type determines the syntax you should use. For example, a connection string for the XML data processing extension is a URL to an XML document. In most cases, a typical connection string specifies the database server and a data file. The following example illustrates a connection string used to connect to the SQL Server AdventureWorks database:

data source=<a SQL Server instance>;initial catalog=AdventureWorks 

A connection string can be configured as an expression so that you can specify the data source at run time. Data source expressions are defined in the report in Report Designer. Data source expressions cannot be defined, viewed, or modified in Report Manager. However, you can replace a data source expression by clicking Override Default to type in a static connection string. If you want to switch back to the expression, click Revert to Default. The report server stores the original connection string in case you need to restore it. To use data source expressions, you must use the data source connection information that was originally published in the report. Shared data sources do not support the use of expressions in the connection string.

Connect Using

Specifies options that determine how credentials are obtained.

Important noteImportant

If credentials are provided in the connection string, the options and values provided in this section are ignored. Note that if you specify credentials on the connection string, the values are displayed in clear text to all users who view this page.

The credentials supplied by the user running the report

Each user must type in a user name and password to access the data source. You can define the prompt text that requests user credentials. The default text string is "Enter a user name and password to access the data source."

Select Use as Windows credentials when connecting to the data source if the credentials that the user provides are Windows Authentication credentials. Do not select this check box if you are using database authentication (for example, SQL Server Authentication).

Credentials stored securely in the report server

Store an encrypted user name and password in the report server database. Select this option to run a report unattended (for example, reports that are initiated by schedules or events instead of user action). If you are using default security, the user name must be a Windows domain account. Specify the account in this format: <domain>\<username>. The account you specify must have log on locally permissions on the computer that hosts the data source used by the report.

Select Use as Windows credentials when connecting to the data source if the credentials are Windows Authentication credentials. Do not select this check box if you are using database authentication (for example, SQL Server Authentication).

If you are using database authentication, select Impersonate the authenticated user after a connection has been made to the data source to allow delegation of credentials, but only if a database server supports impersonation. For SQL Server databases, this option sets the SETUSER function.

Windows integrated security

Use the Windows credentials of the current user to access the data source. Select this option when the credentials that are used to access a data source are the same as those used to log on to the network domain. This option works best when Kerberos authentication is enabled for your domain, or when the data source is on the same computer as the report server. If Kerberos is not enabled, Windows credentials can be passed to one other computer. If additional computer connections are required, you will get an error instead of the data you expect.

A report server administrator can disable the use of Windows integrated security for accessing report data sources. If this value is grayed out, the feature is not available.

Do not use this option if you plan to schedule or subscribe to this report. Scheduled or unattended report processing requires credentials that can be obtained without user input or the security context of a current user. Only stored credentials provide this capability. For this reason, the report server prevents you from scheduling report or subscription processing if the report is configured for the Windows integrated security credential type. If you choose this option for a report that is already subscribed to or that has scheduled operations, the subscriptions and scheduled operations will stop.

Credentials are not required

Specify that credentials are not required to access the data source. Note that if a data source requires a user logon, choosing this option will have no effect. You should only choose this option if the data source connection does not require user credentials.

To use this option, you must have previously configured the unattended execution account for your report server deployment. The unattended execution account is used to connect to external data sources when other sources of credentials are not available. If you specify this option and the account is not configured, the connection to the report data source will fail and report processing will not occur. For more information about this account, see Configuring the Unattended Execution Account.


Click to save your changes.

Community Additions