source database information

Hi,

Yet another question.
Where do reports store information about connection strings to their source databases and credentials that are used to access those databases. So far I have only found that report rdl file contains info about data sources, but it's in format:

<DataSources>
   <DataSource Name="ExperimentSource">
      <rd:DataSourceID>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</rd:DataSourceID>
      <DataSourceReference>ExperimentSource</DataSourceReference>
   </DataSource>
</DataSources>

where the string of x's is actually an alphanumeric string (looks like encoded info).
I want to figure out whether there is more detailed info about the data source for report in some config file and whether I can supply connection string/credential info for my report from some config file.



Answer this question

source database information

  • PlasticLizard

    More copyright infringement... data sources are either embedded in the RDL file or shared as a separate object in the Reporting Services repository.

    Managing Data Source Connections

    A report server connects to external data sources to retrieve data used in reports and data-driven subscriptions. In Reporting Services, a data source is a named collection of properties that describe a connection to an external data source. A data source contains the following parts:

    • Name of the data processing extension used to process the query
    • Connection string used to locate the data source
    • Credentials used to access the data source

    Connection information is typically defined when you create a report or data-driven subscription. However, you can specify a different data source or modify the data source properties after a report is published.

    A data source connection can be embedded in a report or subscription, or defined as a shared data source item. A shared data source item is a separate item that is managed by a report server. You can create a shared data source item that defines a connection to a frequently used data source, and then reference it whenever you need connection information for that data source.

    Shared Data Sources and Report-Specific Data Sources

    Reporting Services provides two ways to define connections to the data sources used in reports and data-driven subscriptions. Both approaches have a similar composition, so you can switch between report-specific data source connections and shared data source items if one approach offers functionality that you want to use. The difference between the two approaches is in how the connection data is stored and managed.

    Report-Specific Data Sources

    A report-specific data source embeds the description of a data source connection in the report definition. Embedded data source connection information can be used only by the report that contains the information. The connection information is internal to the report or subscription (for example, if you view the XML syntax of the report, you can see the connection information in the XML). To define and manage report-specific data sources, use the Data Source Properties page of a report. For more information, see Modifying Data Source Properties.

    Shared Data Sources

    A shared data source is a stand-alone item that describes a data source connection. You can create a shared data source item to provide connection information to multiple reports. You can create and manage a shared data source separately from the reports and data-driven subscriptions that use it.

    A shared data source is reusable across many reports and subscriptions. You can move a shared data source to different folder locations, name a shared data source, and set security to determine its availability. The following icon indicates a shared data source item in the folder hierarchy:

    shared data source icon

    Shared data sources are useful when you have data sources that you use often. Examples of shared data sources that may be useful include the following:

    • A connection to a production server that supports business operations
    • A connection to a frequently-used test server
    • A connection to an employee database to support data-driven subscriptions

    Using a shared data source makes it easier to adjust for changes to the data source. If you move or rename the database or change the database login, you can update the connection string once to effect a corresponding change in all the reports and subscriptions that use the data. You can also disable a shared data source item to prevent report processing.




  • HIRU

    Thanks for information.
    So basically is it possible to alter shared datasource information from outside of Report Designer Can I specify shared datasource info from some type of configuration file and make my report get this info from the file


  • Jerome Le Bateau

    One way is to edit the RDL (XML) of the report, changing the name and ID to the Shared Datasource name and ID on the server. 

    You may also be able to do this from the properties of the report using the web service.


  • source database information