SSRS Data Source

Hi -- just looking for best practices for the data source used for SSRS Custom reports. What I'm currently doing is defining my own data source, which logs in to the database using the Report Server's DB credentials. Are there any pros/cons you can think of for doing this vs. just pointing at Tessitura's own data source for canned reports which logs in using tessApi credentials (as defined in TIM)?

Parents
  • The report template for SSRS reports provided by Tessitura uses the TessituraDB data source, so from an "easy deployment" standpoint, adding another datasource will just add to the steps for report creation if you use those templates. Credentials for that data source really don't make a major difference (generally the tessapi account is sufficient), but if you're at all worried, db_datareader and ImpUsers should all you need for read_only access to impresario and the usual Tessitura procedures.

  • The Tessitura "Canned report" data source I'm talking about is under /Tessitura/Data Sources/ on SSRS, and while your custom report data source is supposed to have the same name, it gets deployed to whatever directory you have defined as TargetDataSourceFolder in your Visual Studio project configuration.

    I suppose the biggest reason not to point your project at that data source would be that if "OverwriteDataSources" got set to "True" by accident, you'd end up overwriting your canned report data source, and while that shouldn't cause a problem unless there's an issue with the new one, I think the risk is probably reason enough to avoid doing it that way.

Reply
  • The Tessitura "Canned report" data source I'm talking about is under /Tessitura/Data Sources/ on SSRS, and while your custom report data source is supposed to have the same name, it gets deployed to whatever directory you have defined as TargetDataSourceFolder in your Visual Studio project configuration.

    I suppose the biggest reason not to point your project at that data source would be that if "OverwriteDataSources" got set to "True" by accident, you'd end up overwriting your canned report data source, and while that shouldn't cause a problem unless there's an issue with the new one, I think the risk is probably reason enough to avoid doing it that way.

Children
No Data