Viewing 15 posts - 50,896 through 50,910 (of 59,098 total)
Heh... Yeaup... I know that... what I want to know is why you need to clone rows like this...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:20 pm
Rob Goddard (4/29/2008)
shalini_pdi (4/29/2008)
Hi,Could any explain how to fetch row by row with out using cursor.
Like everyone has said, you need to give at least demo table structures and...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:16 pm
Oh... not what I was looking for... I wanted to know why you needed to do this, please...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:14 pm
Say... do you happen to have the full test slab for that 16 second version?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:13 pm
Matt Miller (4/29/2008)
(1000000 row(s) affected)
=====================
Jeff's Statistical Median Calc
=====================
(70266 row(s) affected)
SQL Server Execution Times:
CPU time = 70031 ms, elapsed time = 42039 ms.
========================
Matt's Mathematical Median...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:11 pm
And if the query returns a million rows, then what?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 10:06 pm
So... did that work for you or what?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 9:51 pm
Lookup sp_ExecuteSql in BOL... it will do as you ask.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 9:42 pm
Matt... shouldn't that be 0-9?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 9:29 pm
Lemme guess... it's an aggregate view and the WHERE clause you're using contains one of the aggregated columns...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 9:27 pm
Simon_Lo (4/29/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 9:25 pm
Um, where will be be getting @Value_List from? A GUI? If so, you've just opened yourself up to a nasty little case of SQL Injection.
Lemme know... there are...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 9:11 pm
Most of this is straight forward... the comma separated list you want to make can be done by using the technique in the following...
http://www.sqlservercentral.com/articles/Test+Data/61572/
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 8:54 pm
Try using backslash n instead of backslash r. Some text files only have a "linefeed" or "newline" character instead of an actual carriage return.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 8:47 pm
Not if the dupes encompass the key for the group by like this one does...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 8:44 pm
Viewing 15 posts - 50,896 through 50,910 (of 59,098 total)