bradje_1

7 Jan 2010 7:40 PM

Thx Kevin. The explanations and examples are very clear.

Much appreciated,

John Bradshaw

Sameer

8 Jan 2010 3:30 PM

We have changed all the settings to MaxAge of 90 days, including the Raw Performance Data Set..

is this a bad idea?

Kevin Holman

8 Jan 2010 3:39 PM

Possibly.

For the Hourly and Daily - that is fine - if you never need to report on longer than 90 days.

We dont recommend modifying the raw data from 10 days to 90 days. For two reasons: First - raw data is HUGE, and no built in reports access it. Second - it could potentially affect the aggregation jobs if it gets too large.

Normally - my recommendation is to leave raw alone at 10 days - then set the hourly and daily based on your business requirements - understanding that you can keep daily data for a very long time with minimal storage requirements.

Bryce

1 Feb 2010 9:56 PM

Great article. Just an FYI to anyone out there, I got an exception error that my remote connection may not be enabled when I first tried to run the tool.

I removed the default instance name from the command line, tool ran fine.

dwdatarp.exe -s mySQLServerName -d OperationsManagerDW > c:\dwoutput.txt

Bryce

1 Feb 2010 10:04 PM

FYI - I was running the tool locally on my SQL server.

Eric

15 Jul 2010 1:56 PM

Hello Kevin,

the dwdatarp.exe tool return me a configuration dataset to 46% (the current size is 103,508,496 kb)

what are the data in the configuration dataset ?

Thanks

Kevin Holman

15 Jul 2010 4:35 PM

The configuration dataset contains all the discovered properties of all your managed entities, groups, etc.

This can be quite large, especially if you are not on OpsMgr 2007 R2 - as there was a bug where we dont groom the config data in SP1 which was fixed in R2. It can also be large, even in R2 - if you have a lot of poorly written MP's which have discoveries that change frequently - the warehouse keeps a record of the changes necessary for historical reports. This is another reason config churn is such a bad thing. The data will mostly be contained in the ManagedEntityProperty table.

I would just live with the size issue, and work to ensure you are fixing any config churn issues in your environment.

Are you SP1 or R2? Have you evaluated your config churn?

ESA06464

16 Jul 2010 9:10 AM

thank you for you reply

i look at blogs.technet.com/.../what-is-config-churn.aspx to evaluated my config churn and i come back if i have another problem.

for information, i am R2 scom with actually 1000 agents

Kevin Holman

16 Jul 2010 4:39 PM

Eric - when this is really big - it generally means that you have, or had at one time, a MP that was filling the configuration dataset with discovered instance change information. The older Dell and IBM MP's were very bad about this, as are the Microsoft SQL, AD, DNS, etc...

If you want to see what is using all the space... you can run the following query against the warehouse DB:

select distinct top 50 mep.ManagedEntityRowId, me.FullName, Count(mep.managedEntityPropertyRowId) as 'Total'

from ManagedEntityProperty mep WITH(NOLOCK)

LEFT JOIN ManagedEntity me WITH(NOLOCK) on mep.ManagedEntityRowId = me.ManagedEntityRowId

group by mep.ManagedEntityRowId,me.FullName

order by Total desc

Oscar

12 Jan 2011 11:06 PM

How Can I change the value set for configuration dataset iusing query?

Thanks

Kevin Holman

12 Jan 2011 11:23 PM

@Oscar -

Why do you feel you need to modify it?

Oscar

13 Jan 2011 2:37 PM

Hi Kevin,

I't s requirement from a client, they have another SCOM MG and want to replicate the same configuration that they have in the other MG. I was trying to use the DWDATARP.EXE tool, but it fails, so I made the changes with some queries, just I need to modify the last one configuration dataset.

Thanks

I use SCOM 2008 R2 on Windows 2008 R2 and SQL 2008 SP1

Oscar

13 Jan 2011 3:25 PM

Sorry is SCOM 2007 R2 on Windows 2008 R2 and SQL 2008 SP1

every time when I try to use the DWDATARP.EXE tool, I got this.

EXCEPTION : System.Data.SqlClient.SqlException: Cannot open database "Operations

ManagerDW - ds "Client Monitoring data set" -a "Daily aggregations" -m 120" requ

Login failed for user 'REST\usr-ogarza'.

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception

, Boolean breakConnection)

And the account that i'm using has Administrative righhts and SA rights in SQL, so I don't know why is not working fine the tool.

Thanks.

karl

16 Mar 2011 3:06 PM

kevin

that dwdatarp.exe tool is giving me this for my hourly performance data set.

Performance data set Hourly aggregations 400 32,945,816 ( 70%)

is there a way for me to find whats causing it?

thanks

Kevin Holman

16 Mar 2011 3:58 PM

@Karl -

What is the problem? It is totally normal for the Perf Hourly tables to consume the largest percentage of a warheouse. 32GB of perf hourly data is not really all that much. As to tuning this - you should look at this in two dimensions:

1. Retention - set the retention to what is in your SLA for reporting. You are at the default - which is 400 days.

2. Tuning. Run the performance counter queries at blogs.technet.com/.../useful-operations-manager-2007-sql-queries.aspx and determin which ones you dont need - find those rules that collect them - and disable them. Collecting perf data for all objects - when it is a counter you dont care about - will just fill your warehouse with noise.