Viewing 15 posts - 44,341 through 44,355 (of 59,097 total)
Steve Jones - Editor (4/6/2009)
Jeff Moden (4/6/2009)
Heh... no, I get it. But there are still rules of thumb that absolutely must be followed.
There are, but unfortunately we...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 9:49 pm
Heh... brackets... they sure did take a shortcut there. It would be nice if the automatic code generators didn't put those in unless actually required.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 9:47 pm
Steve Jones - Editor (4/6/2009)
We have two developments ongoing. One was our regular developer/week a month that I believe tried to fix some code items. Those are in test now,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 9:28 pm
On the Halloween thingy... that's what I call an "oolie" and it shouldn't make or break an interview. If someone knows it, then it may be a bonus unless...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 7:05 pm
Paul White (4/5/2009)
Also try to remember what it was like when you first started out.
Actually, that's a pretty good point. So is the point about newbies not knowing some...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 7:00 pm
Paul White (4/6/2009)
@jeff,Thanks! But all those smileys have left me emotionally confused :-DPaul
BWAA-HAAA!!! Now that's funny! Like I said, "Welcome aboard"... you're gonna fit in just fine.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 6:46 pm
cs_troyk (4/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 4:57 pm
GSquared (4/6/2009)
Jeff Moden (4/6/2009)
http://www.sqlservercentral.com/Forums/Topic688949-8-1.aspx
My answer would have been... "Thanks for the setup code... please post the code that you've tried so far so we can point you...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 10:42 am
davidandrews13 (4/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 10:16 am
Here's a perfect example...
http://www.sqlservercentral.com/Forums/Topic688949-8-1.aspx
My answer would have been... "Thanks for the setup code... please post the code that you've tried so far so we can point you in the right...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 8:57 am
I agree... Barry's initial response was a bit "curt"... and I also think it was absolutely appropriate.
Look at the list of items asked in the Original post... these are relatively...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 8:50 am
Jack Corbett (4/6/2009)
Jeff Moden (4/4/2009)
I believe the question actually asks "how would you write a trigger that executed another stored procedure but only at...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 8:22 am
Aaron N. Cutshall (4/6/2009)
Jeff Moden (4/6/2009) The first rule that many developers seem to omit is that the code actually has to work. 😉
OK, you got me there!:-P However,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 8:17 am
First, let me take nothing from the article. It's well written and clear. Well done.
However, the following statement seems to destroy whatever utility was intended in the code...
Note...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 8:01 am
GSquared (4/6/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 6, 2009 at 7:36 am
Viewing 15 posts - 44,341 through 44,355 (of 59,097 total)