October 6, 2012 at 3:22 am
All,
is the "Quirky Update" hole is still open in sql 2012 shop too? or is there any patch applied to close the hole?
if yes, what is the workaround for this? I remember Jeff mentioned in one of his interview this was closed. But i am not sure.
karthik
October 6, 2012 at 9:41 am
karthik M (10/6/2012)
All,is the "Quirky Update" hole is still open in sql 2012 shop too? or is there any patch applied to close the hole?
if yes, what is the workaround for this? I remember Jeff mentioned in one of his interview this was closed. But i am not sure.
Wayne Sheffield wrote a great blog article on it including some performance testing.
http://blog.waynesheffield.com/wayne/archive/2011/08/running-totals-in-denali-ctp3/
The "new" method for doing running totals is still slower than the Quirky Update method but not by a whole lot. Better than that, the new method is supported by MicroSoft which helps people avoid that queazy feeling they get when they don't understand something.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 10, 2013 at 7:37 am
Although the new functionality may help with running total, it does not help when trying to roll through a table being able to update a row based on values from the previous row. In other words, anything not aggregate based. Using the TransactionDetail example if I needed to calculate the daily and running performance from one day to the next, I would need to use the formula (Amount - YesterdayAmount) / YesterdayAmount to calculate each rows daily performance. QuirkyUpdate is the only viable/speedy way that I have found to do this.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy