Viewing 15 posts - 43,696 through 43,710 (of 59,097 total)
bob.willsie (5/21/2009)
If so, is the testing process kept up to date? (Years ago I almost went for CDPM certification until I found out half...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 8:50 pm
Thanks for the feedback, Allister.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 8:33 pm
Most flavors of a SAN come with "snapshot" capabilites that solve these types of problems.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 8:24 pm
GilaMonster (5/23/2009)
<sigh>"I detached the DB, deleted the log file and it won't attach. Backups not working either"
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=126304
Head-desk
Why???????????
Ah, ah! There you go again... 😛 No wonder you get the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 8:04 pm
RBarryYoung (5/23/2009)
Say what!!! You're quoting ANSI standards??? ...Alright buddy, Who are you and what have you done with Jeff!
😀
BWAA-HAAA!!! No, I haven't lost my tin hat,...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 8:01 pm
The author of that article didn't do his homework on joins. There is no Natural Join in SQL Server. And, if you research it a bit, if such...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 7:41 pm
Florian Reischl (5/23/2009)
Also very clean to use an tab-lock and an index hint to ensure the order!
Just so long as no one thinks they can do that with a non-clustered...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 7:31 pm
Very cool, Flo. We're getting all of the running total methods out in the open. Care to write a CLR for this bad boy?
The INNER JOIN method, which...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 7:18 pm
Heh... curiously enough, Microsoft and Oracle have two different descriptions of what a "natural" join is.
http://support.microsoft.com/kb/136699
[font="Arial Black"]The Equi-Join and Natural Join[/font]
Almost all joins, including all examples given so far, are...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 6:40 pm
The inline code jumped from 41 seconds at 10,000 rows to 170 seconds for 20,000 rows. In other words, the amount of time increases by a factor of 4...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 2:55 pm
Florian Reischl (5/23/2009)
One question:
Did you figure out if a cross join performs better...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 2:35 pm
That's a "running total" problem. Inline queries are ok for only the smallest of collections. See the following for why...
http://www.sqlservercentral.com/articles/T-SQL/61539/
If you have more than small collections of data...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 1:22 pm
First, this series of articles is good and I won't take anything away from the author on it. Well done.
But, I agree with many of the others when it...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 1:14 pm
Mitch Miller (5/21/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 12:53 pm
Florian Reischl (5/23/2009)
Jeff Moden (5/23/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2009 at 12:42 pm
Viewing 15 posts - 43,696 through 43,710 (of 59,097 total)