Viewing 15 posts - 50,896 through 50,910 (of 59,102 total)
Ummm, then why did you post that you wanted to process rows one at a time? We've all said that's a bad thing... what is it that you're trying...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:46 pm
The other thing to be considered, it what the new rows are in the RecipeLine table are... you'll need to pass those ID's back to the GUI, won't you?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:40 pm
Oh, crud... I just thought of this... If you're using it for that, it's possible that two people could conflict with each other and get the wrong rows...
We've gotta come...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:35 pm
shalini_pdi (4/29/2008)
from one location to other location to reduce the time of dataentry
Perfect... that's what I was looking for. Thank you so much.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2008 at 11:33 pm
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
Viewing 15 posts - 50,896 through 50,910 (of 59,102 total)