Viewing 15 posts - 57,031 through 57,045 (of 59,101 total)
Of course, if you used any one of a thousand or so set based solutions for this problem, you wouldn't have to worry about what a cursor does or doesn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2007 at 8:41 pm
01/01/1900 was also a Monday... kind of convenient, too, because the decimal equivelent for that date is "0".
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2007 at 8:24 pm
Be a bit leary of queries that have an inequality in the WHERE clause especially when a self-join is also present as it may form a "triangular join" which is a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2007 at 8:12 pm
You say you specifically want to use BCP... try BULK INSERT instead... lot's simpler than trying to get around the command shell thing.
Also, you can still use command shell as...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2007 at 7:24 pm
Hat's off to the "remaining partner"... well done, Mr. Jones!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2007 at 7:18 pm
Like I said, unless there is something to force the order of the Task Description (another column, usually), there is no guarantee that the descriptions will come out in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 30, 2007 at 4:42 am
Hi Ryan,
What did you come up with for the largest prime number found and how many prime numbers? I wanna make sure I'm doing it right...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 29, 2007 at 8:31 pm
DO NOT USE @@IDENTITY because it is not scope sensitive... use SCOPE_IDENTITY() instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 28, 2007 at 10:15 pm
Cool... forgot about the mod. Thanks...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2007 at 5:56 pm
Heh... you're right... no underscore... I shouldn't type late at night ![]()
Don't get me wrong... I love BCP! I love it's ability to log,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 26, 2007 at 6:41 am
I agree with some of the others... the tone of the article is a bit distracting and takes away from the good technical content.
It would also be nice if...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2007 at 10:33 pm
Using joins, create an "UPSERT"...
UPDATE where there's a match... INSERT where there isn't.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2007 at 9:30 pm
Might also want to check performance and resource usage of both... statement 2 is a correlated subquery and they can be quite greedy depending on the tables involved.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2007 at 8:37 pm
Heh... and I wouldn't do any of it in DTS.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2007 at 8:30 pm
This is a different problem... can be more easily done with the GROUPING key word in a group by. But not possible either way unless we know what is the PK...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2007 at 8:28 pm
Viewing 15 posts - 57,031 through 57,045 (of 59,101 total)