Viewing 15 posts - 43,081 through 43,095 (of 59,102 total)
mckinnj1 (7/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2009 at 2:34 pm
ali.m.habib (7/8/2009)
Jeff Moden (7/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2009 at 6:31 am
Eswin (7/8/2009)
SET @bcpCommand = 'bcp " select '''+ @expFile +'''" queryout "'
SET @bcpCommand = @bcpCommand + @exptionFile + '" -T -c'
EXEC master..xp_cmdshell @bcpCommand
i don't think you can use '+'...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2009 at 6:29 am
WayneS (7/7/2009)
Lamprey13 (7/7/2009)
This will probably work, but you cannot guarantee that it'll work based on the PK order.
Thanks for pointing that out... I've edited the post to include the necessary...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 8, 2009 at 6:07 am
Heh... do you expect it to guess what to do with your stored proc? You need it to be a valid query.
Also, (local) doesn't seem to work as a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 9:04 pm
rpyerneni (7/7/2009)
I worked on your code. As I told you I have so many links in the content. I splitted the content and inserted the splitted data into a temporary...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 8:54 pm
I've never experienced BCP being slow at anything. Usually, it's the associated query that's slow. Please post both the BCP command and the query being executed by BCP.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 8:49 pm
Paul White (7/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 8:42 pm
Alvin Ramard (7/7/2009)
I don't think anyone mentioned:50 Ways to Leave Your Cursor (Paul Simon)
Here's another one where a name change isn't actually required to still be appropriate...
The good, the bad,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 8:31 pm
I don't use any prefexies in my production databases. The reason is that a table could be changed to a view or vice versa and having a prefix would...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 9:28 am
GSquared (7/7/2009)
Ian Scarlett (7/7/2009)
select id, forename, case when forename = 'Kim' then 1 else 2...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 9:26 am
Bur@ir (7/5/2009)
Now i dont want to have so many rows linked to 1 customer.
Why not? It's what databases do. The other methods will require the additional headaches of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 9:17 am
Paul,
Very cool. The additional sequence table prevents the need for a SELECT or comparison in the code at all and that's important for both concurrency and the prevention...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 7, 2009 at 6:06 am
BWAA-HAA!!! Well, at least now you know why I'm so opposed to any form of "ID Reservation" or "Sequence" table. While it's possible to make such a thing...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 9:45 pm
Idea understood... but that's a sequence table and that's even worse that what's trying to be done for updates unless you're very, very, very careful and you use a 3...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 6, 2009 at 9:11 pm
Viewing 15 posts - 43,081 through 43,095 (of 59,102 total)