InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 23 May 2013 04:42:46 GMT20http://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxHi Robb, here's some stuff for you to play with. Note that the join to the recursive part in the rCTE is [i]critical[/i].[code="sql"]DROP TABLE #NumbersSELECT TOP 1000000 --000 n = ROW_NUMBER() OVER (ORDER BY a.name), CalcValue = CAST(NULL AS BIGINT)INTO #NumbersFROM master.dbo.syscolumns a, master.dbo.syscolumns bCREATE UNIQUE CLUSTERED INDEX CIn ON #Numbers ([n] ASC) -- (1,000,000 row(s) affected)SET STATISTICS IO ONSET STATISTICS TIME ON-- 'Quirky' updateDECLARE @Lastval INT = 0, @CalcValue BIGINTUPDATE #Numbers SET @CalcValue = CalcValue = (@Lastval + n), @Lastval = n-- (1,000,000 row(s) affected) / CPU time = 2968 ms, elapsed time = 3079 ms.-- Table #Numbers... Scan count 1, logical reads 3113, physical reads 6, read-ahead reads 3146, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.-- Recursive CTE;WITH Calculator (n, CalcValue) AS ( SELECT n.n, CalcValue = CAST(n.n AS BIGINT) FROM #Numbers n WHERE n.n = 1 UNION ALL SELECT n.n, CalcValue = n.n + c.n FROM #Numbers n INNER JOIN Calculator c ON n.n = c.n + 1 -- nice --INNER JOIN Calculator c ON c.n + 1 = n.n -- nice --INNER JOIN Calculator c ON c.n = n.n - 1 -- slow --INNER JOIN Calculator c ON n.n - c.n = 1 -- slow --INNER JOIN Calculator c ON c.n - n.n = -1 -- slow )SELECT n, CalcValue FROM CalculatorOPTION (MAXRECURSION 0)-- (1,000,000 row(s) affected) / CPU time = 33297 ms, elapsed time = 36161 ms.-- Table 'Worktable'. Scan count 2, logical reads 6000001, physical reads 0, read-ahead reads 0, lob logical reads 0, lob physical reads 0, lob read-ahead reads 0.SET STATISTICS IO OffSET STATISTICS TIME Off[/code]There's some more [url=http://www.sqlservercentral.com/Forums/Topic873124-338-2.aspx#bm873773]here[/url].CheersChrisMTue, 25 May 2010 09:51:52 GMTChrisM@Workhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspx[quote][b]Robb Melancon (5/24/2010)[/b][hr]So I'm running into the following:The statement terminated. The maximum recursion 100 has been exhausted before statement completionAnd looks like the max is 32,000, did you run this on the million row table?[/quote]OPTION (MAXRECURSION 0)I'm still looking for the thread, Robb...and yes, a million rows in about 9 seconds using a recursive CTE. BTW credit to Paul White for discovering the performance improvement returned by ensuring the clustered index is unique.Mon, 24 May 2010 09:26:37 GMTChrisM@Workhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxAlthough the max recursion is only a bit over 32K, any change in criteria will restart that recursion. You could easily run it on millions of rows... or it could crap out at 33k, it all depends on the data distribution.Mon, 24 May 2010 09:19:42 GMTGaradinhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxSo I'm running into the following:The statement terminated. The maximum recursion 100 has been exhausted before statement completionAnd looks like the max is 32,000, did you run this on the million row table?Mon, 24 May 2010 09:16:28 GMTRobb Melanconhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxHi RobbThere were some performance comparisons posted here earlier in the year. IIRC the running totals update did a million rows in about 6 seconds, the rCTE method took a little less than twice that.Mon, 24 May 2010 08:47:21 GMTChrisM@Workhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxOk, so I got it. My question now is how does this perform relative to doing the same thing with fast forward read only cursors? I can answer that by implementing this in some more tests but just wondering if you guys have a guess...Here is the completed code:[code="sql"]create table #DMVRunningPerformance ( Seq int, LongPosition_bt bit null, AssetID_in int null, Symbol_vc varchar(255), DayID_in int, Status_vc varchar(255) null, MV float, DailyPerf float null, RunningPerf float null) CREATE CLUSTERED INDEX [indexdown] ON #DMVRunningPerformance ( [Seq] ASC, [LongPosition_bt] ASC, [AssetID_in] ASC, [DayID_in] DESC ) WITH (SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY] insert into #DMVRunningPerformance values (1,1,100,'IBM',75006,NULL,201048.8987,NULL,NULL)insert into #DMVRunningPerformance values (2,1,100,'IBM',75005,NULL,200841.5658,NULL,NULL)insert into #DMVRunningPerformance values (3,1,100,'IBM',75004,NULL,200321.7043,NULL,NULL)insert into #DMVRunningPerformance values (4,1,100,'IBM',75003,NULL,201120.0467,NULL,NULL)insert into #DMVRunningPerformance values (5,1,100,'IBM',75002,NULL,201779.8805,NULL,NULL)insert into #DMVRunningPerformance values (6,1,100,'IBM',75001,NULL,201651.3917,NULL,NULL)insert into #DMVRunningPerformance values (7,1,100,'IBM',75000,NULL,201651.3917,NULL,NULL) declare @AssetID_in int=-1, @NDAssetID_in int=-1, @LongPosition_bt bit=0, @Status_vc varchar(255)=NULL, @NewGroup_bt bit=1, @DailyPerformance float, @RunningPerformance float, @NDMarketValue float ;WITH Calculator AS ( -- Anchor row, tr.Seq = 1 SELECT thisrow.Seq, thisrow.Symbol_vc, thisrow.DayID_in, thisrow.MV, DailyPerf=CAST((thisrow.MV-nextrow.MV)/nextrow.MV AS FLOAT), RunningPerf = CAST((thisrow.MV-nextrow.MV)/nextrow.MV AS FLOAT) FROM #DMVRunningPerformance thisrow INNER JOIN #DMVRunningPerformance nextrow ON nextrow.Seq = thisrow.Seq + 1 WHERE thisrow.Seq = 1 UNION ALL -- first recursion will be Seq = 2 (thisrow.Seq = 2, lastrow.Seq = 1) SELECT thisrow.Seq, thisrow.Symbol_vc, thisrow.DayID_in, thisrow.MV, DailyPerf = CAST((thisrow.MV-nextrow.MV)/nextrow.MV AS FLOAT), RunningPerf = ((1 + lastrow.RunningPerf) * (1 + CAST((thisrow.MV-nextrow.MV)/nextrow.MV AS FLOAT))) - 1 FROM Calculator lastrow INNER JOIN #DMVRunningPerformance thisrow ON thisrow.Seq = lastrow.Seq + 1 INNER JOIN #DMVRunningPerformance nextrow ON nextrow.Seq = thisrow.Seq + 1 )SELECT Seq, Symbol_vc, DayID_in, MV, DailyPerf, RunningPerf FROM Calculatordrop table #dmvrunningperformance[/code]Mon, 24 May 2010 08:39:40 GMTRobb Melanconhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxRobb, looks straightforward - but can you please edit and if necessary correct correct the line beginning - [i]So 75006 Daily is... [/i]CheersChrisMMon, 24 May 2010 08:26:35 GMTChrisM@Workhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxThanks for the input guys. The rows need to be calculated in dayid desc order. Here are the expected results.AssetID_in Symbol DayID_in MV DailyPerf RunningPerf 100 IBM 75006 NULL 201048.8987 0.001032321 0.001032321 100 IBM 75005 NULL 200841.5658 0.002595133 0.003630133 100 IBM 75004 NULL 200321.7043 -0.003969482 -0.000353759 100 IBM 75003 NULL 201120.0467 -0.003270067 -0.003622669 100 IBM 75002 NULL 201779.8805 0.000637183 -0.002987795 100 IBM 75001 NULL 201651.3917 0 -0.002987795 100 IBM 75000 NULL 201651.3917 0 -0.002987795It's a bit odd because you need to start on the second row (Todays MV - Yesterdays MV divided by Yesterdays MV) to get the first rows performance but the running is done first row to second row. So 75006 Daily is (201047.8987-200841.5658)/200841.5658 and running is 1 + Current Running (which is 0 on day 75006) * 1 + Daily minus 1. I realize the Running Performance seems backwards meaning that the value for the entire period is actually stored on the first day of the period, but this is done for a reason which is more than you probably want to know about calculating market performance for periods.... anyway hope this calrifies a little more.Mon, 24 May 2010 08:20:09 GMTRobb Melanconhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspx[quote][b]Robb Melancon (5/21/2010)[/b][hr]Running SQL2008Also Ten Centuries, your solution violates the rules of using the "Quirky Update" by using a Join. I'll add a link to the article on "Quirky Update".[url]http://www.sqlservercentral.com/articles/T-SQL/68467/[\url]I don't know that this method is ultimately what I will use as I am skeptical about using it in a production environment, but it is the quickest performing alternative to cursors that I have found.[/quote]Hi RobbA recursive CTE will do the job. Like Seth, I'm unsure of which direction (relative to DayID_in) you wish to run the calculation for RunningPerf. Here's an example which should get you started:[code="sql"];WITH Calculator AS ( -- Anchor row, tr.Seq = 1 SELECT thisrow.Seq, thisrow.Symbol_vc, thisrow.DayID_in, thisrow.MV, DailyPerf = CAST((nextrow.MV-thisrow.MV)/thisrow.MV AS FLOAT), RunningPerf = CAST(NULL AS FLOAT) FROM #OrderedData thisrow INNER JOIN #OrderedData nextrow ON nextrow.Seq = thisrow.Seq + 1 WHERE thisrow.Seq = 1 UNION ALL -- first recursion will be Seq = 2 (thisrow.Seq = 2, lastrow.Seq = 1) SELECT thisrow.Seq, thisrow.Symbol_vc, thisrow.DayID_in, thisrow.MV, DailyPerf = CAST((nextrow.MV-thisrow.MV)/thisrow.MV AS FLOAT), RunningPerf = lastrow.RunningPerf FROM Calculator lastrow INNER JOIN #OrderedData thisrow ON thisrow.Seq = lastrow.Seq + 1 INNER JOIN #OrderedData nextrow ON nextrow.Seq = thisrow.Seq + 1 )SELECT Seq, Symbol_vc, DayID_in, MV, DailyPerf, RunningPerf FROM Calculator[/code]Note that if you have a unique clustered index on the seq column, as in the example, the SELECT will run in a similar timeframe to a running totals update.If you want to use the results of the SELECT to update another table, then you would be wise to run the results into another table rather than attempting an UPDATE FROM ... with the rCTE as a table source - performance can be poor.The SELECT returns 6 of the 7 rows because of the INNER JOIN 'nextrow'. Logically you can't get a value for the last row in any case because it has no [i]next[/i] row! However, you can make the row appear in your output by fiddling the join criteria.Come back if you need help with this. The important point to remember about recursive CTE's is that only the result of the last iteration is 'exposed' to the next.CheersChrisMMon, 24 May 2010 04:40:47 GMTChrisM@Workhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxI'm still a little unclear on your requirements. Can you provide the results you are trying to get?This is a guess and might be the whole thing you're trying to avoid, but what about changing the sort order to ASC on day_id and then using this:[code="sql"]update #DMVRunningPerformance set @DailyPerformance=DailyPerf=CASE WHEN @NewGroup_bt=1 THEN 0 ELSE (MV - @NDMarketValue)/ @NDMarketValue END, @RunningPerformance=RunningPerf=CASE WHEN @NewGroup_bt=1 THEN 0 ELSE ((1 + @RunningPerformance) * (1 + @DailyPerformance)) - 1 END, @NDMarketValue=MV, @NewGroup_bt=0FROM #DMVRunningPerformance OPTION (MAXDOP 1)[/code]Fri, 21 May 2010 15:54:56 GMTGaradinhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxRunning SQL2008Also Ten Centuries, your solution violates the rules of using the "Quirky Update" by using a Join. I'll add a link to the article on "Quirky Update".[url]http://www.sqlservercentral.com/articles/T-SQL/68467/[\url]I don't know that this method is ultimately what I will use as I am skeptical about using it in a production environment, but it is the quickest performing alternative to cursors that I have found.Fri, 21 May 2010 14:41:39 GMTRobb Melanconhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxRobb, can you please confirm that you are running on SQL Server 7 or 2k?Fri, 21 May 2010 07:43:26 GMTChrisM@Workhttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxTry this[code="sql"]create table #DMVRunningPerformance ( Symbol_vc varchar(25), DayID_in int, MV float, DailyPerf float null, RunningPerf float null) CREATE CLUSTERED INDEX [indexdown] ON #DMVRunningPerformance ( [Symbol_vc] ASC, [DayID_in] DESC ) WITH (SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY] insert into #DMVRunningPerformance values ('IBM',75006,201048.8987,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75005,200841.5658,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75004,200321.7043,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75003,201120.0467,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75002,201779.8805,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75001,201651.3917,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75000,201651.3917,NULL,NULL) declare @NewGroup_bt INT, @DailyPerformance float, @RunningPerformance float, @NDMarketValue floatset @NewGroup_bt =0; set @RunningPerformance=0; update B set @NDMarketValue=B.MV, @DailyPerformance = (@NDMarketValue-C.MV)/C.MV , B.DailyPerf=@DailyPerformance, @RunningPerformance= ((1 + @DailyPerformance)*(1 + @RunningPerformance) ) - 1 , @NewGroup_bt=@NewGroup_bt+1, B.RunningPerf=@RunningPerformance FROM #DMVRunningPerformance b INNER JOIN #DMVRunningPerformance C ON b.DAYID_IN=C.DAYID_IN+1select * from #DMVRunningPerformancedrop table #DMVRunningPerformance[/code]Fri, 21 May 2010 06:48:35 GMTGopi Mulukahttp://www.sqlservercentral.com/Forums/Topic925065-8-1.aspxThis is an extension to another topic I had posted but I decided to split it off as the problem is different than the original problem of replacing the cursor/while loop with a faster method.So I am stuck on a problem I am having using the "quirky update" method for replacing a cursor/while loop. The root of the issue is that the update compares row n to row n+1 and updates the contents of row n+1. What I need is a comparison of row n to row n+1 but then update the contents of row n.Here is the code that displays the problem.[code="sql"]create table #DMVRunningPerformance ( Symbol_vc varchar(255), DayID_in int, MV float, DailyPerf float null, RunningPerf float null) CREATE CLUSTERED INDEX [indexdown] ON #DMVRunningPerformance ( [Symbol_vc] ASC, [DayID_in] DESC ) WITH (SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF) ON [PRIMARY] insert into #DMVRunningPerformance values ('IBM',75006,201048.8987,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75005,200841.5658,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75004,200321.7043,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75003,201120.0467,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75002,201779.8805,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75001,201651.3917,NULL,NULL)insert into #DMVRunningPerformance values ('IBM',75000,201651.3917,NULL,NULL) declare @NewGroup_bt bit=1, @DailyPerformance float, @RunningPerformance float, @NDMarketValue float update #DMVRunningPerformance set @DailyPerformance=CASE WHEN @NewGroup_bt=1 THEN 0 ELSE (@NDMarketValue-MV)/MV END, @RunningPerformance=CASE WHEN @NewGroup_bt=1 THEN 0 ELSE ((1 + @RunningPerformance) * (1 + @DailyPerformance)) - 1 END, DailyPerf=@DailyPerformance, RunningPerf=@RunningPerformance, @NDMarketValue=MV, @NewGroup_bt=0FROM #DMVRunningPerformance OPTION (MAXDOP 1)select * from #DMVRunningPerformancedrop table #DMVRunningPerformance[/code]Note that I can't change the order as it would completely change the performance numbers. I am trying to avoid having to roll through the set a second time to shift the numbers up. So to clarify, the MV of row n is compared to MV of row n+1 to get daily performance. This performance number (and the running performance) need to be stored in row n, not row n+ 1.Thanks in advance,RobbThu, 20 May 2010 06:49:27 GMTRobb Melancon