Viewing 15 posts - 43,096 through 43,110 (of 59,063 total)
In the face of bad software, improperly written T-SQL, and poorly designed databases, the rating of the hardware and it' support systems means absolutely nothing.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 6:38 pm
My apologies, Brian, but you've been "exiled" way too long and have forgotten the meaning of it all... as have many.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 6:26 pm
GilaMonster (7/4/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 6:22 pm
Eswin (6/26/2009)
I want to fetch one row at a time and then satisfy the conditions following while @@row_count 0 and while @@fetch_status = 0 .
That would be the problem......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 6:21 pm
mjarsaniya (7/4/2009)
sorry
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 6:09 pm
You bet, Wayne. Thanks for answering my seemingly unrelated questions. They go far in helping me understand the needs of folks so I can setup certain tests for...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 12:36 pm
WayneS (7/4/2009)
Jeff Moden (7/4/2009)
WayneS (7/3/2009)
@jeff - would you mind trying out this little piece of code and let me know how fast it is on your "computer in a deathbox"?:-D
No...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 12:07 pm
WayneS (7/3/2009)
And, just to be complete, I ran this test again including Lynn's CTE method (DelimitedSplit):XML: 1571/1100/1350/1134/1130
Tally: 1429/1313/1306/1317/1288
CTE: 6283/6221/6292/6445/6569
Heh... looks like the Tally table won twice there.
But, I agree... joining...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 12:05 pm
Jeff Moden (7/4/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 11:27 am
Last but not least, Wayne... I ran your code and the XML section returns nothing. Perhaps the forum ate some of your code. Can you attach the code,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 11:22 am
Also, please answer the following questions:
How many time have you had to split something in real production work that actually consisted of more than 8k bytes? What was it...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 11:13 am
WayneS (7/3/2009)
@jeff - would you mind trying out this little piece of code and let me know how fast it is on your "computer in a deathbox"?:-D
No problem... would you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2009 at 11:06 am
And, yes, Digs... that test shows that a 1000 element parameter was split in less than a heartbeat for both methods. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2009 at 7:50 pm
Dang it... I thought you were really on to something Lynn. Still, a very cool slice of code you rendered that will smoke any While Loop. Consider that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2009 at 7:49 pm
It'll be interesting what the performance is when you get this all done.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2009 at 2:56 pm
Viewing 15 posts - 43,096 through 43,110 (of 59,063 total)