Viewing 15 posts - 44,551 through 44,565 (of 59,097 total)
Roy Ernest (3/18/2009)
I think all of you has made some progress with Fox. He actually gave the Table structure?? Wow. I am impressed with all of your patience..
I cannot believe...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2009 at 7:45 pm
That's why I suggested attaching the first 10 lines of the file... so I can see what the termination character is in binary.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2009 at 7:36 pm
Thanks for the feedback... and yes, that's precisely what I was talking about. You also don't need to spend a lot of time deleting that way, either (although, like...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2009 at 7:31 pm
foxjazz (3/18/2009)
J, my dba wife pointed it out to me last night that set based solutions are not always superior to cursors.
She's confusing things like the use of triangular...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2009 at 7:14 pm
Lynn Pettis (3/18/2009)
Chris Morris (3/18/2009)
foxjazz (3/18/2009)
{} is much better than BEGIN BEGIN BEGIN BEGIN END END END END
Heh quite possibly - but the count of BEGIN - END pairs goes...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 18, 2009 at 7:06 pm
BWAAA-HAAA!!!! Hey Lynn! Now you know one of the reasons I don't like case sensitive databases. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
March 17, 2009 at 6:49 pm
Bob Hovious (3/17/2009)
Knock rings about what? (This is not a sarcastic question, Jeff.)
The Thread... if you want it to be a good place to meet for those that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 17, 2009 at 8:57 am
You guys are starting to knock rings about that and that's not right.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 17, 2009 at 5:45 am
Sheesh!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 11:43 pm
steve dassin (3/16/2009)
you have my regret that I misjudged the maturity level of some readers here.
Man... get over yourself... I used to respect your maturity until you started using cheap...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 11:38 pm
Bob Hovious (3/16/2009)
I thought perhaps there was a misunderstanding about the question. When I saw that Flo had answered to your satisfaction I...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 11:20 pm
If the formatting of each element is pretty much cast in stone, then a straight forward method may be in order...
Here's the test data...
--===== Create a demonstration table (This is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 11:14 pm
It's going to be tough to troubleshoot this without some test data and a listing of the code that does the Bulk Insert. If the data has private information...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 10:20 pm
harish_ravi (3/16/2009)
but i dont think its working for comparing data with duplicate values.
like the below.
DECLARE @v1 TABLE (id INT, txt VARCHAR(100))
DECLARE...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 10:17 pm
Heh... "Survey says... ding, ding, ding, ding, ding... STUFF! Look it up in Books Online". Bruce is spot on.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 16, 2009 at 10:08 pm
Viewing 15 posts - 44,551 through 44,565 (of 59,097 total)