May 6, 2010 at 9:26 am
Hi All,
Please share the best practices to be followed to cinfigure MDW. I am goint to implement MDW to capture database growth,cpu usages,memory utilization and all other paramaters.
Chandu
May 6, 2010 at 1:51 pm
chandu.ade (5/6/2010)
Please share the best practices to be followed to cinfigure MDW. I am goint to implement MDW to capture database growth,cpu usages,memory utilization and all other paramaters.
Follow the fine Microsoft documentation and everything will be Okay.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.May 6, 2010 at 1:56 pm
For my servers, I've just accepted the defaults, and on a couple of them increased data retention and also compressed a few tables and indexes. Nothing you can't easily learn along the way.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
December 14, 2012 at 7:34 am
Folks,
I am trying to build a SQL Server jobs historical warehouse. This is to run reports to see how a certain jobs are peperforming over few months on a number of instances.
For that I would like to use MDW. Everything is on SQL Server 2008.
How would I go about it?
Any output is trully appreciated.
thanks!
Bee
if one wants it.. one will justify it.
December 15, 2012 at 4:46 am
I've had lots of trouble with this half-baked 'feature'.
A couple of dozen monitored instances ended up in an mdw db over 700GB data and 300-odd GB log.
Looking at the code inside explains some of the issues, it was probably written by trainees.
Make sure you assign good storage to both data and logs. This one caught me out, the SAN was not nippy and the clearing up wasn't happening properly on the datafile. Had to drop the whole thing twice and start over again with new defaults (choosing to retain less rather than more).
Watch carefully the size growth in the first few weeks and pre-allocate enough space. It can grow very large very fast.
Be careful, some snapshots are every 15seconds, that can lead to huge tables that are very slow to query afterwards. You may want to change them to 300 secs perhaps.
Also stagger the Agent jobs manually, you don't want all over them hitting the central db at the same time (clearly the defaults are not meant for multi-instance usage:hehe:)
There are bugs in the procs as well, worth doing an internet search.
Yes it comes free with SQL, but it is worth as much.:-D
Cheers,
JohnA
MCM: SQL2008
December 17, 2012 at 7:06 am
Its a pitty that every second DBA must re-create a wheel for very common things: I want to see how my job is performing for the last 6 months.. I need to build a data mart for it.. sucks..
if one wants it.. one will justify it.
December 17, 2012 at 7:20 am
boris_shvartsman (12/17/2012)
Its a pitty that every second DBA must re-create a wheel for very common things: I want to see how my job is performing for the last 6 months.. I need to build a data mart for it.. sucks..
SQL already provides this history. Just go to the properties of SQL Server Agent then change the history tab from the default values of 1000/100 to something significantly larger.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply