Viewing 15 posts - 44,236 through 44,250 (of 59,101 total)
Heh... ok, Paul. From the way you were talking, I thought you were on to an improvement.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2009 at 7:35 pm
Thanks for your concern. If I'm not mistaken, PIVOT can do multiple aggregations... I just gotta look back in my notes because I don't use PIVOT for all the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2009 at 7:25 pm
All of that may be true... I just hope they never remove the capability because it is an option. It's kind of like cursors... I generally deplore their usage...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2009 at 7:52 am
Paul White (4/12/2009)
Jeff Moden (4/11/2009)
http://www.sqlservercentral.com/articles/T-SQL/63681/
Performance meaurements are at the bottom of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2009 at 7:39 am
Paul White (4/11/2009)
Jeff Moden (4/11/2009)
...A persisted computed indexed column would do very nicely here.
Hey Jeff,
It would, but an ordinary column would be my first choice, mainly because persisted computed columns...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2009 at 7:36 am
Outstanding... thanks for the post and the code, Paul... I'll check it out. That's what I love about forums. Lots of folks with lots of ideas.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2009 at 7:31 am
Bob Hovious (4/11/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 9:27 pm
I agree... it would probably be better to not move the data before processing. And, if that's still somehow necessary, I've had great success with just dropping the table...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 8:15 pm
Paul White (4/11/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 8:07 pm
To add to what Flo stated... if you insert more than one row with an IDENTITY column, you can use OUTPUT to capture all of the IDENTITIES created as a...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 3:40 pm
A well formed crosstab can be almost twice as fast as a Pivot and a whole lot easier to read, to boot. Please see the following articles...
http://www.sqlservercentral.com/articles/T-SQL/63681/ (Performance...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 3:38 pm
I think you could probably cut way down on the scans and rowcounts if you did a little "Divide'n'Conquer" to do some pre-aggregations to temp tables and join on those.
Of...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 3:25 pm
Bob Hovious (4/11/2009)
Hey... who are you callin' an oxymoron!? :unsure:
Heh... so you know that guy, too, huh? 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 3:16 pm
Heh... no... that's certainly not ring knocking in my book. It takes a certain amount of hair to stand up in front of a worldwide community and speak. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 3:09 pm
You bet... thanks for the feedback, Flo.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2009 at 3:04 pm
Viewing 15 posts - 44,236 through 44,250 (of 59,101 total)