Type a name for the shared data source, which is used to identify the item within the report server folder hierarchy.
Provide information about the shared data source. This description appears on the Contents page.
- Hide in list view
Select this option to hide the shared data source from users who are using list view mode in Report Manager. List view mode is the default view format when browsing the report server folder hierarchy. In list view, item names and descriptions flow across the page. The alternate format is details view. Details view omits descriptions, but includes other information about the item. Although you can hide an item in list view, you cannot hide an item in details view. If you want to restrict access to an item, you must create a role assignment
- Enable this data source
Select to enable or disable the shared data source. You can disable the shared data source to prevent processing for all reports and models that reference the item.
- Data source type
Specify the data processing extension that is used to process data from the data source. Report server includes data processing extensions for SQL Server, Analysis Services, Oracle, SQL Server Integration Services, SAP, XML, ODBC, and OLE DB. 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 SQL Server data sources.
- 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 AdventureWorks2008R2 database:
data source=<a SQL Server instance>;initial catalog=AdventureWorks2008R2
For more examples and information about different ways to specify a connection string, see Data Connections, Data Sources, and Connection Strings (SSRS).
- Connect using
Specify options that determine how credentials are obtained.
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.
- Credentials supplied by the user running the report (Connect using)
Each user is prompted to 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 (Connect using)
Store an encrypted user name and password in the report server database. Choose 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 database credentials, but only if a database server supports impersonation. For SQL Server databases, this option sets the SETUSER function.
- Windows integrated security (Connect using)
Use the Windows credentials of the current user to access the data source. Choose 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 authentication 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 (Connect using)
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.