Viewing 15 posts - 44,581 through 44,595 (of 59,101 total)
By the way, Goldie... no special test is required for the non-breaking space because of the way I detect characters that need to be replaced with a space.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 9:08 am
Goldie Graber (3/15/2009)
I'm going to test it out at work tomorrow.
One part I don't quite understand is this:
--===== Replace all EntityCodes with the actual ascii character...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 8:58 am
Yep... I agree... knowledge and time are part of the real world items that are frequently missing in that area. Like Perry stated, I just don't want anyone to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2009 at 9:22 am
megham10 (3/15/2009)
my field is like "Field"(Surrounded by "").But how to make BCP Format .Pls guide me.
Sergiy is correct... OPENROWSET or a text based linked server may do the trick easily....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2009 at 9:15 am
Adi Cohn (3/15/2009)
You can find an explanation here – http://msdn.microsoft.com/en-us/library/ms191516(SQL.90).aspxAdi
Unfortunately, the MS documentation on this subject doesn't tell you how to handle text qualified strings that use quotes with...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2009 at 9:11 am
steve dassin (3/14/2009)
foxjazz (3/13/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2009 at 9:08 am
Jack Corbett (3/15/2009)
Barry,Just making sure you noticed, but Goldie said that the CLR is not an option in this case. I had suggested it originally as well.
Heh... yeah... but...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2009 at 9:02 am
I'll also kick in that I'm amazed at the attitude of so many DBA's, especially System DBA's. The code is part of the server and bad code should be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 15, 2009 at 8:59 am
RBarryYoung (3/14/2009)
OK, this is the most disturbing thing that I have read in a while. Read it closely. Brrrr...
Oooooh myyyyyy.... absolutely chilling. "Forgive them, Lord, for they...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 11:50 pm
foxjazz (3/14/2009)
I haven't experienced a case where I could write a stored proc, without t-sql language .... I would love to write my stored procs in c#.
foxjazz (3/14/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 11:46 pm
RBarryYoung (3/14/2009)
Jeff Moden (3/14/2009)
RBarryYoung (3/14/2009)
I know that this'll drive Jeff crazy, but I actually think that this would work better as a CLR Trigger.
It might... but Nah... "we don need...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 11:19 pm
Here's the code with the last step of counting the actual words...
--===== Replace all HTML tags with nothing
WHILE CHARINDEX(' CHARINDEX('<',@HTMLText)
SELECT @HTMLText = STUFF(@HTMLText,
...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 11:15 pm
Sorry Goldie... I forgot the last step... I'll be right back...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 11:02 pm
RBarryYoung (3/14/2009)
I know that this'll drive Jeff crazy, but I actually think that this would work better as a CLR Trigger.
It might... but Nah... "we don need no stinkin' CLR"...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 11:01 pm
As much as I praise their use, there are some things that the Tally table won't beat a WHILE loop at... cleaning strings using STUFF is one of those things...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2009 at 10:56 pm
Viewing 15 posts - 44,581 through 44,595 (of 59,101 total)