Hi, I thinks SP2 does the right action when there is no available value bund to the parameter. A report should validate its parameters before processing. While sp1 just throws out the warning message for the empty parameter and other report items can process, such so the generated report does not make sense for the end users. Additionally, if you have any concern about this, also you can submit a feedback at https://connect.microsoft.com/SQLServer/Feedback . thanks, Jerry

I am trying to troubleshoot an SSRS 08 report that broke when SP2 was applied. The problem appears related to a hidden ReportParameter bound to a potentially empty DataSet. It appears that prior to SP2, query-based ReportParameters could be null, but after applying SP2, the report throws an error: The 'HiddenReportParameter' parameter is missing a value I'm curious whether this could be related to VSTS bug # 393879, "Data-Driven subscription fails if a NULL value is returned when it is mapped to the report parameter, which accepts a NULL value." An obvious solution is to add a dummy row to the dataset to prevent it from ever being empty, but I'm mainly interested in an explanation of why this would have broken in SP2. thanks.