Viewing 15 posts - 51,781 through 51,795 (of 59,091 total)
p.s. All the times, scan, and read counts for my previous post were on SQL Server 2k... the optimizer in 2k5 was a little more kind to the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 11:55 pm
Hey, before I get started on this, "thank you" to all of the folks that took time to provide
some feedback, whether it was pro or con. That's what...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 11:44 pm
Heh... although I'd like to take credit for it, I think that was when they were having date problems on the forum. And thanks for the compliment.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 5:55 pm
Forget the cursors, forget the LIKEs... and remember that ISNUMERIC treats "-", and a whole bunch of other characters as valid numeric characters. NEVER use ISNUMBER as IsAllDigits because...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 3:50 pm
shamas saeed (3/14/2008)
Yes You can do with as all above says or use ## to use it in procedure
Global temp tables are a bad idea... if more than one instance...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 12:53 pm
John Rowan (3/14/2008)
I just wanted to thank you all for your military service.
Awesome, John. Thank you, Sir!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 9:51 am
Chrissy (3/14/2008)
I am very much a newbie, and I just wanted to say this forum has actually given me confidence to start training as a SQL DBA in my...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 9:50 am
Anders Bendix Nielsen (3/14/2008)
That is simply one of the best articles on RBAR I have ever seen!Excellent!! 🙂
Thanks for the great feedback, Anders.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 8:10 am
ALZDBA (3/14/2008)
If our dev's would only apply the basic rules and also try to write their
code at least in two different ways,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 8:09 am
Nick M. (3/14/2008)
The links to UPDATE are to the UPDATE() function, not the UPDATE statement syntax, which is 1 line above in the index. 🙂
Thanks for pointing that out, Nick....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 8:01 am
David McKinney (3/14/2008)
Very good article.I just think RBAR would catch on more, if it were pronounced AR-BAR. (Sorry 😉 )
Maybe "our Bar" would work even better 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 7:55 am
Zarko Jovanovic (3/14/2008)
what about this:update table1
set table1.column1 = #table.column1, table1.column2 = #table.column2
from table1, #table
where table1.pk=#table.pk
That's fine because the table being updated is in the FROM clause and is properly joined......
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 7:54 am
Heh... a friend of mine gave me a lapel button that says "I've survived damned near everything!" If your under 40, it's your turn and I'll be happy to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 14, 2008 at 12:06 am
I believe you also need to do a DBCC FREEPROCCACHE before a DBCC DROPCLEANBUFFERS if you trully want to make sure the execution plan is cleared.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 11:49 pm
Dang... I thought for sure it stood for "Customers Test Problems" 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
March 13, 2008 at 11:44 pm
Viewing 15 posts - 51,781 through 51,795 (of 59,091 total)