Multiple Data Sources

Is there away to change the datasource at the time of deployment of a report? I know there is a production and debug deployment for specifying URLs and Folders. Is there anyway to specify the datasource, so you can have one for production and another for debug / test? Do you keep two datasources in the project? The production datasource already exists in the target environment.

Any help would be appreciated.

Thanks!

DotNetNow

Well:

We keep (as I think all people do) environments for test and production - so we test everything with RS and then deploy to the production server and just change (or point to the production environment

within the Project Properties or within the data sources within the Project itself such as:

Data Source=(For Example the Server Name);Initial Catalog=(For Example the data base name)

That means that when a developer is done doing what a developer does - the DataSource Name is changed to the QA group - all applications are deployed to the QA group -

The QA group does what they do and they have a production person change the Data Source parameters to the production environment.

That is one of the features I really like with RS is the deployment capabilities - it all relies on what you define within the data sources within the project or the properties of the project.

Hope this helps!

Multiple authentication methods in scale-out deployment

Will SSRS 2008 support multiple authentication methods in a scale-out deployment (intranet / extranet scenario)? Books Online (July CTP) seems inconsistent in addressing this.

In the entry Server Architecture (Reporting Services) BOL states:

If your deployment requires multiple authentication providers, you can configure a scale-out deployment. For more information, see Planning for Scale-Out Deployment (Reporting Services).

When forwarding to the indicated link Planning for Scale-Out Deployment (Reporting Services), BOL states:

Report server instances in a scale-out deployment must have the same type of authentication extension. If you created a custom authentication extension, you must deploy and use that extension on all nodes.

Because of this restriction, you cannot configure a scale-out deployment to support simultaneous intranet and extranet access to the same report server database through separate report server instances where each instance is configured for different authentication types and authorization rules.

Which is it?

Regards,

Scott

It should be the second one (not supported). I will forward your feedback to the documentation folks.

Multiple authentication providers is under consideration for a post-2008 release.

Multiple authentication methods in scale-out deployment

Will SSRS 2008 support multiple authentication methods in a scale-out deployment (intranet / extranet scenario)? Books Online (July CTP) seems inconsistent in addressing this.

In the entry Server Architecture (Reporting Services) BOL states:

If your deployment requires multiple authentication providers, you can configure a scale-out deployment. For more information, see Planning for Scale-Out Deployment (Reporting Services).

When forwarding to the indicated link Planning for Scale-Out Deployment (Reporting Services), BOL states:

Report server instances in a scale-out deployment must have the same type of authentication extension. If you created a custom authentication extension, you must deploy and use that extension on all nodes.

Because of this restriction, you cannot configure a scale-out deployment to support simultaneous intranet and extranet access to the same report server database through separate report server instances where each instance is configured for different authentication types and authorization rules.

Which is it?

Regards,

Scott

It should be the second one (not supported). I will forward your feedback to the documentation folks.

Multiple authentication providers is under consideration for a post-2008 release.