Viewing 15 posts - 47,281 through 47,295 (of 59,095 total)
I can't go. I've got tickets and everything but something came up today and I can't go. :crying: Somebody take pictures for me.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 10:01 pm
"Novice" my butt :)... you've been paying attention. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 9:56 pm
Well I'll be damned... didn't even notice until just now... 12,000+ posts... Steve owes me a shirt or two! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 9:35 pm
ggraber (11/12/2008)
I was really looking for some basic guidelines.I really have come to love the readability of CTEs.
I just wanted to make sure I wasn't compromising performance.
I guess if...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 9:28 pm
ggraber (11/12/2008)
BTW Jeff, I've been meaning to ask you this:How on earth do you have time to give such thorough answers to so many people on the forums???
I'm really amazed!!
Heh......
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 9:21 pm
Sorry... almost forgot... borrowed on Carla's good code and expanded the test data set a bit for my testing...
CREATE TABLE PersonRecord ( PersonID int NOT NULL, Version int NOT NULL,DEDate...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 9:03 pm
You should see what happens with the correct and incorrect indexing. Adams code (using his because Carla rated it as the fastest) is more than twice as fast as...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 8:42 pm
Sorry... looks like those were CPU times.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 8:37 pm
Carla Wilson (11/12/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 7:54 pm
Will Riley (11/12/2008)
Why not construct a UDM (Unified dimensional model) layer over the reporting database instead and create report models for your report builders to hit. That's...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 7:50 pm
ggraber (11/12/2008)
Jeff Moden (11/11/2008)
Thanks for the feedback... you sure you're all set?
Not really, Jeff. Thanks for asking. 🙂
What I'm really looking for is performance comparison between CTE and Derived Tables.
I...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 7:46 pm
I've gotta dog-ear this page... all those in favor of developers having write access to production boxes, raise your hand! 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 6:20 pm
Patrick Russell (11/12/2008)
Jeff Moden (11/11/2008)
Also, can you post your restructured WHERE clause, please?
Below is the code using the restructured WHERE clause you posted. In testing I saw no noticable difference;...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 6:17 pm
goodguy (11/12/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 6:13 pm
AndrewMurphy (11/12/2008)
Oh....and look into shooting the developer 😀
Um... for what? Using a paltry 40 MB of TempDB? Fragementing the disk because TempDB started out insanely small. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 12, 2008 at 6:11 pm
Viewing 15 posts - 47,281 through 47,295 (of 59,095 total)