Viewing 15 posts - 49,381 through 49,395 (of 59,099 total)
Ok... now, to understand how the function works, you have to read the following...
http://www.sqlservercentral.com/articles/TSQL/62867/
If you want a super deep knowledge of how to do splits well beyond what's in that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 10:19 am
mick burden (7/7/2008)
DECLARE @Now...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 10:16 am
If you're not going to finish it, you shouldn't start it. 😉 What do you want to race on... again? 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:25 am
Lynn Pettis (7/7/2008)
Just one little problem with your code above. The closing paren for the CREATE TABLE #FileDetails is included in your comment. It took me a bit...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:23 am
Steve Jones - Editor (7/7/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:18 am
I don't know why folks say that CLR's perform better and are more scalable... it's absolutely not true in about 99% of the cases and several of us have beat...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 9:13 am
You're right... it's an awesome study! Proves what I've been saying all along about some folks in the IT business... they don't look, they don't read, they don't understand......
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:58 am
Part of the problem is that you're not measuring time correctly... you're including the time it takes for Barry to build his example... I added a bit to Barry's existing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:51 am
Dang... thanks for the catch, Ken... I normally list that article and plumb forgot...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:30 am
Marios Philippopoulos (7/7/2008)
I don't know much about sp_OA* procedures, but I think they come with their own baggage of problems, and in any...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:25 am
Ok, thanks for the feedback...
By the way... sorry I forgot to post the simple code example... just in case anyone else is interested...
DECLARE @SomeString VARCHAR(1000)
SET @SomeString...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:05 am
Thanks,
Just a couple more questions...
1) Which date are you listing... Create, Modified, or Last Accessed?
2) Are you allowed to use sp_OA* procedures?
3) Do you really need the date and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 8:02 am
David Naples (7/7/2008)
You can't do this directly, as the CREATE PROCEDURE or ALTER PROCEDURE statement has to be the first in the batch.
Ummm... maybe not directly, but you can...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 7:55 am
Thanks for letting us know what the problem was, Jim... I think you're on the right track.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 7:50 am
... and, here's a bit of simple code to play with...
If you cannot create a Tally table, please post back... we have other ways to skin the same cat. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2008 at 7:49 am
Viewing 15 posts - 49,381 through 49,395 (of 59,099 total)