Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

SSRS report parameters set after publishing to report manager

Posted on 2016-10-06
1
Medium Priority
?
116 Views
Last Modified: 2016-10-10
Hello experts -

We are in the process of migrating from SSRS 2005 to SSRS 2008 and have come across an issue with default report parameters set at the design level (in SSRS before deploying) vs. report parameters set at the report manger level (in the web interface after publishing). One of our developers has written a script to extract all the reports from the 2005 collection and drop it into the 2008 collection.  The default report parameters that are set at the report manager level (after deploying) are not migrating but the default report parameters that are set at the design level in SSRS are.

I am wondering if there is a way to find out which default report parameters are set after deployment? I found a script (attached) to give me default report parameters that have been setup in SSRS, which is the first half of the equation. However, I am hoping that there is a place in the ReportServer database (or maybe somewhere else?) that will tell me if default report parameters are setup in report manager, along with what those reports and parameters are.

I hope all that made sense. I know I rambled a bit...
Find-Reports-with-Defaults.docx
0
Comment
Question by:Lisa Callahan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 16

Accepted Solution

by:
Megan Brooks earned 2000 total points
ID: 41832519
It makes a lot of sense. "By design" Report Server preserves certain parameter settings once a report has been published. Exactly when it ignores new published settings and when it overwrites saved settings is a mystery I have never wanted to spend a lot of time figuring out. Instead, I have usually followed a process something like this:

1. Publish an update to a report
2. Validate the report
3. If it doesn't work as expected, delete it from the report server and publish again.
4. If it still doesn't work, there is a problem with the report itself and not with however Report Server decided to mangle the parameter settings.

An alternative to #3 is to manually go into Report Manager (on the Report Server) and change the parameter properties to match what is currently in the RDL published in step 1. This can avoid having to delete. If the properties don't change often and you don't want to delete, this may be the solution.

Deleting a report before republishing doesn't matter in simple reports, but it can wipe out history information, as well as caching and snapshots, subscriptions, etc.

It should be possible to write automation to check for and correct discrepancies between published parameters and those in the RDL being published, using the catalog web service. I've never had to go that far, and I don't know what surprises you might run into.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Data architecture is an important aspect in Software as a Service (SaaS) delivery model. This article is a study on the database of a single-tenant application that could be extended to support multiple tenants. The application is web-based develope…
Use this article to create a batch file to backup a Microsoft SQL Server database to a Windows folder.  The folder can be on the local hard drive or on a network share.  This batch file will query the SQL server to get the current date & time and wi…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
This is my first video review of Microsoft Bookings, I will be doing a part two with a bit more information, but wanted to get this out to you folks.

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question