Viewing 15 posts - 47,161 through 47,175 (of 59,102 total)
Heh... you guys are missing it... OP wants to know why performance IMPROVED so much after the upgrade so they can go back to the original database and make it...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 7:15 pm
I agree... do an estimate to figure out what the total size should be with a year of data and add 20 to 25% to that number. Set the...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 7:11 pm
If they're all like the one you posted with a couple of cursors calling another sproc that probably has another cursor in it, you could be in for some real...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 7:06 pm
Please post what you tried so we can see things like what you tried to GROUP BY. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:57 pm
The data should actually match the table definition... instructions in the atricle everyone has posted would really make this easy.
Msg 515, Level 16, State 2, Line 3
Cannot insert the value...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:51 pm
metro17 (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:44 pm
James A. Lawrence (11/18/2008)
Sorry! Already mentioned above!
Still, thanks for the thought.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:45 pm
I've got a hell of a lot of comments to make about this article... but, let me summarize, instead...
[font="Arial Black"]"Oh... very well done. Should be required reading for everyone...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:17 am
BWAA-HAA! I guess it's because I need more coffee, as well! Maybe that qualifies. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:09 am
Just remember that you will get an advisory about total row length exceeding 8060 bytes if you use more than a very small handful of columns in the same table...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:07 am
Garadin (11/18/2008)
Jeff Moden (11/18/2008)
The really good part about it all is that no matter what goes wrong, I always learn something new even if it's only how to "read minds"...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 6:02 am
mpdillon (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:58 am
vkundar (11/18/2008)
gborasaniya you are right as this in data warehousing environment mainly in ETL we have constraints on using or creating indexes. we need to deal...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:35 am
Chris Morris (11/18/2008)
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:30 am
Dooza (11/18/2008)
... and was setup like this by the developers.
Heh... of that, I have no doubt. Thanks for the feedback, Steve. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
November 18, 2008 at 5:27 am
Viewing 15 posts - 47,161 through 47,175 (of 59,102 total)