Viewing 15 posts - 51,376 through 51,390 (of 59,091 total)
Start here...
http://www.sqlservercentral.com/articles/Test+Data/61572/
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:59 am
Heh... Never got around to finishing those... can't find any developers that can follow the first commandment...
"Though shalt have no greater database authority than the DBA."
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:56 am
So, you're saying that a DBA must learn all possible languages that may be compiled into a CLR and have the ability to review the source code from same? ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:40 am
No, no... that's one of the 10 Commandments of Developers...
"Thou shalt not commit RBAR" 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:25 am
Shaun McGuile (4/1/2008)
Jeff are those the 'Three Rules'? 😀akin to Asimov and Clarke
Heh... no... these are... 😉
[font="Tahoma"]Jeff Moden's Three Rules of DBA's.
1. A DBA may not injure data or performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 6:15 am
ashoknegi84 (4/1/2008)
i have a table like
empname empid empsal
---------------------------
abc 1 ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 5:42 am
rbarryyoung (4/1/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 5:41 am
SQLZ (4/1/2008)
command on all tables that are more than 10% fragmented.
I know I can use sys.dm_db_index_physical_stats to get this...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 5:40 am
rbarryyoung (4/1/2008)
And as far as I'm concerned, IN and EXISTS OK to use. They are just as fast as Joins when used correctly and greatly aid code clarity.
WHERE IN...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2008 at 5:35 am
Heh... I'm thinking that's more than two options right there 😉 Lets see... DTS, OSQL query, SP_OA* sprocs... there's a couple more, but I forget.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 11:58 pm
Yes... don't use either... use an INNER JOIN instead.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 11:47 pm
Extract into what? Are the files all in the same format? We need just a little more info.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 11:45 pm
p.s. A join to a Calendar table would be even more effective...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:58 pm
tickler_foryou (3/31/2008)
I have a Order_date column where order dates are captured in SQL server 2005 DB, I need to find the order dates that falls on Week Days only...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:56 pm
You'd be amazed what it can do... as you've seen, it'll do splits. It'll also fill in missing dates, generate multiple rows for each row according to a "QTY",...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 31, 2008 at 10:33 pm
Viewing 15 posts - 51,376 through 51,390 (of 59,091 total)