Hi All,
Hope someone can help here. Since installing Service Pack 2 onto our SQL 2005 instances our report models are not working correctly. When selecting fields within the models as filters, and getting them to prompt when the report is run, the ordering of the data within the filters does not match the selected ordering in the model definition. The ordering is random each time the report is run.
This issue does not happen when setting the filter up, the data appears in the correct order, but when running the report the filter data is incorrect.
I have spent the last 4 hours building a new system and testing this with each stage of service packing. The RTM version of SQL 2005 is ok, SP1 is also OK, but when SP2 is applied the ordering fails.
Any ideas?
Many thanks in advance.
Regards
Nick
An update to this issue just in case it may help others.
I logged a call with Microsoft relating to this issue and the product support specialist managed to reproduce the issue at their end. It was passed up to the product teams and the reponse has come back that it is now designed this way even though it worked prior to SP2.
The specific issue is:- Dropdown parameter boxes on reports created using report builder do not adhere to the ordering specified in the report model at runtime, although they do at design time.
As we were adding parameter boxes allowing users to select from almost 1000 branch codes the fact that it isn't ordered and appears in a random order is obviously an issue that has meant we can no longer use report builder.
The workaround suggested by Microsoft is to index the underlying tables so that the table scans of the branch codes scan indexes instead and return ordered lists, as the index is already ordered. Unfortunately I cannot do this as my tables are indexed for performance, and I can't change them to fix an issue that shouldn't (in my personal opinion) be there in the first place.
Hope this helps anyone else in the same situation.
Nick
No comments:
Post a Comment