Viewing 15 posts - 58,996 through 59,010 (of 59,099 total)
Not sure, folks, but I think the original question was about having temp tables with the same name running in stored procedures that run at the same time. The answer,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 20, 2004 at 10:09 pm
You've made it a bit difficult on yourself... the following should do nicely and should do 70,000 records in something less than 10 seconds on a good server...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 5, 2004 at 2:52 pm
Yeah, Wayne has confirmed what I've heard... you can do some really nasty things through xp_shell. Maybe you shouldn't go there. Just create the BCP job in a batch file...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2004 at 10:26 pm
Of course, Microsoft documentation is always 100% correct ![]()
What you may want to try, instead, is calling BCP using xp_shell... that is unless you...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2004 at 7:17 am
Calvin,
If your server is set to CONCATENIZATION OF NULL YIELDS NULL, then you will need either COALESCE or ISNULL unless you preset the variable to something other than NULL.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2004 at 10:19 pm
Richard,
I believe that, with SQL 2000, there is a BULK INSERT role where you no longer have to grant a user "SA" rights just so they can use the BULK...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2004 at 10:07 pm
Cedar72,
You've been bitten by the "time" element of datetime data types... try this as your WHERE clause...
The DATEADD/DATEDIFF thingy accurately removes...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2004 at 9:51 pm
Jana,
Yeah, before you say anything, I see the bug, too. Here's the corrected code... had to assume that you would have something in first name and last name fields to...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2004 at 9:29 pm
Jana,
Here's a real simple solution using the power of a NULL being returned when a NULL is concatenated... the key is to concatenate each space or comma with each name...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2004 at 9:19 pm
Regardless of which method you use to do the renumbering, if Col1 is an IDENTITY column, you would need to include the following line just before the update...
SET IDENTITY_INSERT tablename...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 16, 2004 at 6:05 am
I dunno... David Burrows' solution doesn't use CONVERT or any form of overt concatenization (+) and may be faster as a result. In the beginning, I used LEN, then graduated...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2004 at 9:51 pm
Dummy me... missed the formatting thing... thought he didn't understand the "ELSE". Nice job, Rockmoose!
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2004 at 3:21 pm
Rockmoose,
>We do have a problem if they have breaks around midnight .. though
Yeah, I had the same problem and decided that it wasn't so bad to use a temp...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 13, 2004 at 3:14 pm
Sukhoi,
I can't post back to your original post, either... I did take a look at the code you posted and all I can say is ...
Daaannnnng that's a lot of...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2004 at 9:46 am
Not sure from your description of the problem but I think an INSERT statement would probably do... since you didn't mention which 3 parameters you wanted to save nor which...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 12, 2004 at 9:32 am
Viewing 15 posts - 58,996 through 59,010 (of 59,099 total)