Viewing 15 posts - 52,846 through 52,860 (of 59,091 total)
Ture enough... and I've not tried the SSIS solution for this, but (just something to consider) the DTS solution was horribly slow compared to the BULK INSERT that used the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2008 at 6:47 am
For the original problem given where certain parameters determine which function may be exercised and returned, a simple CASE statement would be in order whether it be for a RBAR...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 18, 2008 at 6:44 am
Ok, thanks, Matt... good information. I'll get my arms around all this "new" 2k5 stuff, soon.
But I'm pretty sure that Scope_Identity isn't "login" sensitive as you suggest. That...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 10:49 pm
We'll see... when you figure out the correct answer for the real question being asked, post it here.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:56 pm
Guess the next questions would be...
How many of you make the mistake of letting developers create their own tables? How many of you allow that to occur without...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:50 pm
Step 1... find the person that designed the ID column... take him/her to dinner... feed him/her 2 pound porkchops... at point blank range with a sling shot!
Ok... having said that,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:42 pm
Heh... let's see... take a urine test, hair test, background check, credit check, education check, check for bounced checks, check for references, check for traffic and felonly violations, etc, etc,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:25 pm
Matt Miller (1/14/2008)
It looks something like
declare @nextid as...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:17 pm
jkurtis (1/17/2008)
theres a couple problems with that.The 1st is that I'm on SQL2000.
And people wonder why I get ticked at some users... what were you thinking when you posted this...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:10 pm
I'm thinking "simple answer" here... what were the grants on the old box?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:05 pm
Changing the format of the "date" column is just a repetitition of the original mistake... for more reasons than will fit in this meager window, you must NEVER store dates...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 9:03 pm
Quick show of hands... how many require that table and column comments be included in table definitions? Next question... How many require that they be done correctly? š
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 8:44 pm
I wondered when you were going to get to that point...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 8:08 pm
Daniel Storm (1/17/2008)
- Iām not asking about what a deadlock is (been...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 7:57 pm
Ah... sorry... I see what you're getting at, now... yes, you are correct... only way to trully avoid the RBAR of the function is to, in fact, limit to a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 17, 2008 at 7:43 pm
Viewing 15 posts - 52,846 through 52,860 (of 59,091 total)