Viewing 15 posts - 44,251 through 44,265 (of 59,097 total)
Oh... be careful folks... this wonderful and great interplay of thoughts and ideas to come up with some absolutely outstanding code all share the same common fault... they all can...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 2:11 pm
The answers about sargeable predicates have already been pretty well covered on this thread, so I'll not go there.
Going back to the original question, the first code snippet uses correlated...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 1:55 pm
arup_kc (4/9/2009)
Here is a situatrion where without GO, its throwing an error.
ALTER TABLE...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 1:47 pm
Apologies for the large delay in responding...
At this point, I'm not sure... guess I'd have to play with it. I'd probably clean all the data so that anything that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 1:05 pm
Sheng (4/7/2009)
Jeff Moden (4/6/2009)
Soooo.... does that mean you're happy now?
...... I can't follow you.:-) I just want to discuss if I've made a right decision about generating this column in...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 12:58 pm
vishal.chawla (4/7/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 12:51 pm
Jim Russell (4/8/2009)
Don't you dare...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 12:28 pm
Lynn Pettis (4/7/2009)
Jeff Moden (4/7/2009)
Only they don't get to come back after calming down.
BWA-HAA!!! That's not a fault... that's a feature. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 12:20 pm
mosaic (4/9/2009)
quick and dirty - but handy for ad-hoc use:Set query output to text
sp_MSforeachtable @command1=" SELECT '?', COUNT(*) FROM ?"
Um... maybe. If you have tables like what are...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 12:11 pm
Sorry... I forgot... here's the code I used for the INT truncation which is the fastest method for truncating a date that I know of.
CREATE FUNCTION dbo.jbmTrunc
--===== Function to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 11:46 am
andrew gothard (4/11/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 11:41 am
Well... I did it. Thank goodness they extended the deadline of PASS 2009 Session Abstracts. I'll be there one way or another this year.
I saw that...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 11:02 am
GilaMonster (4/11/2009)
Shane Redding (4/11/2009)
In regards to the below, perhaps you should go work for the microsoft sql server team as GOTO is not uncommon in TSQL. 🙂
Just because the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 10:57 am
GilaMonster (4/11/2009)
Bob Hovious (4/11/2009)
Okay... how many people here advocate the use of GOTO statements in T-SQL?
I do, solely for error handling in SQL 2000. Since there isn't a TRY-CATCH construct...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 10:52 am
steve dassin (4/10/2009)
Jeff Moden (4/10/2009)
steve dassin (4/10/2009)
Do you realize that for over thirty years the relationship between the sqland and relationaland can be categorized by one word - 'Failure'.
Yep......
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 1:46 am
Viewing 15 posts - 44,251 through 44,265 (of 59,097 total)