Viewing 15 posts - 43,096 through 43,110 (of 59,102 total)
Heh... dang it... I had the right thread after all. That code above is slow. Where all the other methods take something less than 16 ms to split...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 9:02 pm
Sorry... wrong thread.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:50 pm
Digs (7/5/2009)
I havent built it yet. Because what comes first the chicken or the egg,...
By the way... the answer to that question is the "egg" because a chicken can only...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:30 pm
Where'd Digs go? He owes us a post with his solution...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:26 pm
wesigler (7/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:24 pm
There may be even a better way to avoid deadlocks on this. Combine the Insert with the Select... I believe you'd still need the TABLOCKX because you're needing to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:12 pm
smunson (7/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:06 pm
smunson (7/6/2009)
"SERIALIZABLE
Specifies the following:
Statements cannot read data that has been modified but not yet committed by other transactions.
No other transactions can modify...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 7:52 pm
smunson (7/6/2009)
Jeff Moden: I'd really appreciate your input on this...
It might not be what you expect... my input is that in this modern day of computers and other new fangled...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 7:44 pm
wesigler (7/6/2009)
My approach is to come up with a couple of options and then look at the pros and cons of each.
Then, my approach would be to avoid all deadlocks...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 7:34 pm
sanjeev40084 (7/6/2009)
see if this works:http://sqlservercode.blogspot.com/2005/09/split-comma-delimited-string-fast.html
Heh... that blog contains the same method we've already talked about in this thread.... except it's usually just called a "Numbers" or "Tally" table instead of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 3:12 pm
Sergiy (7/5/2009)
Jeff Moden (7/2/2009) Andrew already did exactly what I would do...
I would not.
There was a member of Led Zeppelin, John Paul Jones.
Would not be happy seeing his name...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 2:54 pm
I'm still wondering about that primary key.... What happens if a company needs more numbers? Maybe it's in one of the previous posts. Haven't had time to study...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 2:46 pm
wesigler (7/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 8:25 am
Heh... it does help but there's still one piece of info missing.... so, lemme ask the same question as before...
My apologies for being thick... just trying to figure this out...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 6:22 am
Viewing 15 posts - 43,096 through 43,110 (of 59,102 total)