November 21, 2011 at 2:31 am
Ok I think I have found the solution.
I created a new dataset with just the tax value and used it the calculation below:
(SUM(Fields!ThisWeekLatestViewSales.Value)/First(Fields!TaxRate.Value, "Tax"))
Seems to work now.
Thanks for the help with this.
November 21, 2011 at 2:34 am
Hi
I agree with you about the NOLOCK statement. But its the standards set by the DBAs to use on the report server. so I have to follow them!
November 21, 2011 at 2:49 am
rcr69er (11/21/2011)
HiI agree with you about the NOLOCK statement. But its the standards set by the DBAs to use on the report server. so I have to follow them!
I'd get something in writing if I were you. The fact that you require "tax" points to this being a financial report, so when the figures are incorrect due to a dirty read caused by NOLOCK (that's right, I mean when not if, it will happen) who do you think the company will blame? The designer of the report is top of the list.
November 21, 2011 at 3:03 am
There already is written documentation 😀
November 21, 2011 at 3:35 am
rcr69er (11/21/2011)
There already is written documentation 😀
I more meant something absolving you of responsibility, preferably signed by the DBA that enforced the NOLOCK, his manager and your manager.
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply