Viewing 15 posts - 35,461 through 35,475 (of 59,102 total)
Nils Gustav Stråbø (1/6/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 6:42 pm
toddasd (1/6/2011)
Jeff Moden (1/6/2011)
toddasd (1/6/2011)
declare @a varchar(100)set @a = 'Number of files=4'
select substring(@a, 17, len(@a))
:blink:
To me, looks like he wanted the "4" from the string. So, you know, taking a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 6:38 pm
WayneS (1/6/2011)
Jeff Moden (1/6/2011)
... Credits to Navy beans ...Huh?
Think "Dollars to Donuts". 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 6:23 pm
Steve Jones - SSC Editor (1/7/2011)
It's most likely a people/process failure more than SQL Server, but it does give ammunition to the idea that...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 6:19 pm
lijnenjoost (1/7/2011)
Ps thread age doesn't realy matter, as long it's usefull for the next one that is reading the post.
I absolutely agree with THAT! 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 6:05 pm
Jeff Moden (1/7/2011)
SQLkiwi (1/6/2011)
Jeff Moden (1/5/2011)
Personally, I'd prefer a NULL to be returned instead of an error...
Hmmm. That's an interesting question. I don't like the idea of NULL...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 5:52 pm
SQLkiwi (1/6/2011)
Jeff Moden (1/5/2011)
Personally, I'd prefer a NULL to be returned instead of an error...
Hmmm. That's an interesting question. I don't like the idea of NULL being overworked...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 5:47 pm
jswong05 (1/7/2011)
To parse sophisticated text data (with multiple rules), you should use high level language like C# (it is easy to write and debug), you could embed C# into...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 5:35 pm
Sorry I didn't comment on this series of articles before, Gail. They're absolutely awesome and should be required reading for everyone from SQL Neophyte to Ninja. Very well...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 4:41 pm
CELKO (1/7/2011)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 4:13 pm
Heh... oh my... just on a "what if" whim, I just created a new splitter using the Tally Table. It's 3 times faster the DelimitedSplit8K proc and has flatter...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 2:46 am
Houston, we have a different winner. The test table is identical as before except I constrained my test data generator to only 8 values per row. The Tally...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 7, 2011 at 12:05 am
Houston, we have a winner.... and it's not the Tally Table. The recursive CTE splitter is about twice as fast as the DelimitedSplit8k function on 1000 rows of 800...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2011 at 11:53 pm
LutzM (8/12/2010)
There is an even fast...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2011 at 11:22 pm
Post withdrawn. I was speaking out of school and haven't actually tested against that particular split function.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2011 at 11:21 pm
Viewing 15 posts - 35,461 through 35,475 (of 59,102 total)