January 8, 2009 at 10:52 am
I'm wondering if anyone else has had this issue and how they handled it. In my location, we have 4 different environments (Development, QA, UAT, Production). When developers create a report, the deployment of the .RDLs onto the servers are handled by various release teams (which may be different per environment). To make the report available, the deployment member will navigate to the Report Manager for their environment and then they will upload the report (after the DBA has created the shared data source within the "Data Sources" folder).
Here's the problem. When developing a report, the shared data source (lets assume the name ds_Test) is noted as DataSourceReference>ds_Test /Data Sources/ds_Test</DataSourceReference (note the addition of "/Data Sources'"). I noticed, however, that if the developer does this...if they specify the /Data Sources/...to their local .RDL file within the SSRS project, it will not work within BIDS. So we're left needing this specified in one area and not in another and a manual step by developers to make the quick edit.
This brings me to my question: Is there a way to automatically handle the addition of the "/Data Sources/" text to the XML document during deployment via Report Manager? Alternately, is there a setting within Reporting Services that will default all reports to look at the "Data Sources" folder whether it is explicitly set or not? I could create my own custom upload utility that would handle this in code...but I'd prefer not to if possible.
Any thoughts would be greatly appreciated...
January 16, 2009 at 9:27 am
When you are using a shared datasource it is not very complicated when all reports use one permissions to the same database so all a developer needs is RDL and solution files to upload to all testing and deployment servers. So all deployment servers needs a copy of the current version of the database and a shared datasource to that database with reporting services running that same configurations in all places. Check the thread below for similar problem.
http://qa.sqlservercentral.com/Forums/Topic629406-162-1.aspx#bm630174
Kind regards,
Gift Peddie
January 16, 2009 at 9:45 am
Thanks…although I believe what that thread states only works when a report is being deployed from BIDS (as opposed to being uploaded via Report Manager).
In BIDS, it is perfectly fine to select a shared data source, create a report, set the properties of the project to deploy the data sources to a common "Data Sources" folder and then to deploy the report. One can then navigate to the report server and view the report without errors. This will not work, however, if you upload a report through report manager instead of deploying through BIDS.
For uploading…if you took the same steps as noted above, the data source MUST be in the same folder as the report. The only way to get around that is to manually edit the xml file prior to uploading to add "/Data Sources/" in to the dataSourceReference tag (see below in bold/underline).
DataSourceReference>/Data Sources/ds_dataSourceName</DataSourceReference
Given that the environment I work in deploys all reports via report manager (as release engineers wouldn't create a project just to deploy reports), I am looking to see if there is a way to have developers manually change the rdl file once they are complete (especially since the rdl, with the "/Data Sources/" tag, now won't work in BIDS!!!).
January 16, 2009 at 10:08 am
I am also talking about deployment to report manager and RDL file editing is not needed but you need the solution files in the development folder. That is the same way Microsoft creates sample reports that are run any where in the world. I have deployed to servers in four locations I don't know physically I just upload my RDL and all solution files in the development folder. Editing Microsoft propriety RDL will introduce complications.
Look at it this way upload all reports in one folder without BIDs and just make sure your reports work and use that folder to move to other deployment folders because the ReportSever DB runs your RDL files in the catalog table. Complications are introduced by people who don't know software development.
Kind regards,
Gift Peddie
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply