Is there a way to reduce the polling interval for Data going to scomDW and scomAC database ?
Hi, My DBA is complaining that there is too much polling from SCOM to his database. He mentioned that every second there are 5 to 6 request per second. Is there a way to reduce SCOM polling interval? If so where is the place to change it?
August 6th, 2012 9:17pm

Hi SCOM doesn't poll - SCOM Management Servers sends data continuously to both databases. Alert data and state data is then synchronised every 3 minutes. Data Flow - http://blogs.technet.com/b/momteam/archive/2007/10/30/event-alerts-perf-data-flow-in-opsmgr-2007.aspx Synchronising Data - http://blogs.technet.com/b/jonathanalmquist/archive/2010/01/24/how-and-when-is-data-written-or-synchronized-to-the-data-warehouse.aspx You can't change these settings. SCOM should have its own SQL Servers and if you have virtualised these then you should take care as to placement with other guests so as not to have resource contention. Disk IO is key here. Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2012 2:26am

Hi, Thanks for the information. My DBA commented that my SCOM writes information into the database too often. Like 1 sec 4 to 5 request? would this be normal? If so, will this be better if i reduce the number of monitoring counters ? BTW my RMS server and database is on the same physical server. Reply Quote Propose As Answer Edit Delete
August 7th, 2012 2:53am

Hi I don't understand what your DBA is complaining about. This is the way SCOM works. It collects data. It writes it to the databases. It might well be that SQL is not configured well or that the underlying Disk I\O is too high for the underlying storage. These links might help: A collection of a few blogs that look at hardware requirements and SQL IOPS: http://technet.microsoft.com/en-us/library/bb735402.aspx http://blogs.technet.com/b/momteam/archive/2008/04/10/opsmgr-2007-hardware-guidance-what-hardware-do-i-buy.aspx http://blogs.technet.com/b/momteam/archive/2008/06/24/performance-iops-for-the-db-and-dw-in-opsmgr-2007.aspx http://blogs.technet.com/b/jonathanalmquist/archive/2009/04/06/how-can-i-gauge-operations-manager-database-performance.aspx For performance reasons, I'd move the RMS away from SQL but if your users are happy with performance of the console \ notifications then SCOM is working fine. Are both OperationsManager databases on the same SQL Server that are with the RMS? How to move the databases is listed here: http://technet.microsoft.com/en-us/library/cc540402 And some real world guidance here: http://blogs.technet.com/b/kevinholman/archive/2010/08/26/moving-the-operations-database-my-experience.aspx http://blogs.technet.com/b/kevinholman/archive/2010/08/25/moving-the-data-warehouse-database-and-reporting-server-to-new-hardware-my-experience.aspx Cheers Graham Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2012 3:01am

Yes, my Operational manager database is also on the same physical server. All my SCOM components expect for agents are in the same physical server. For the time being, we have to look for a work around. My question who be how to reduce this? Will monitoring less servers help ? Anyway, that server is using 3.8G/4.0GB and I agree that disk I/O is high.
August 7th, 2012 3:16am

How many agents do you have? With only 4 GB of RAM and having SQL and RMS on the server then there will be performance issues. If you can't increase the specification of the server or move the components to seperate servers then your only option is really to monitor less: - remove agents you don't need to monitor - remove management packs that you don't need But I suspect that the server you have will always struggle. As you mention the RMS, I assume you are on SCOM 2007 R2 (rather than 2012) so the sizing guide might help: http://blogs.technet.com/b/momteam/archive/2009/08/12/operations-manager-2007-r2-sizing-helper.aspx http://technet.microsoft.com/en-us/library/bb432135.aspx Deployment Scenarios - http://technet.microsoft.com/en-us/library/bb735402 Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2012 4:34am

Hi, I have a total of 11 agents that my RMS is monitoring. There are also devices about 10 devices monitoring as well. My SCOM is 2007 R2
August 7th, 2012 4:03pm

Hi For that many agents you should be fine. I'm struggling to understand your DBAs concerns - SCOM is functioning as it should. 1) Is the SQL Server \ RMS virtualised or a physical server? 2) Are there any other databases (other than the SCOM databases) on the SQL Server? 3) What is the problem with the RMS writing to the database? If you want to reduce Disk IO then you can either remove the agents or remove the management packs but you are monitoring so little, I suspect that it won't have much affect unless you have some custom monitoring that is generating excessive data. Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2012 4:08pm

1) Is the SQL Server \ RMS virtualised or a physical server? The are on the same physical server, no VM is installed 2) Are there any other databases (other than the SCOM databases) on the SQL Server? Yes there is another database that is for another software installed in the server 3) What is the problem with the RMS writing to the database? The problem is we have recieved an alert stating that the database is unavailable during that instance. However, my SCOM workflow recovered. SCOM advise to check with DBA why was DB unavailable. My DBA replied that it is because SCOM is writing too much data into database, so he recommends to "reduce" the frequency of data that is been written. He does not believe that i cannot set SCOM to reduce the frequency of SCOM writing data. So I had no choice but to log a case to MS and write into the forum to convinced him.
August 7th, 2012 5:09pm

Hopefully he understands now. Let us know if you need more information. Regards GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2012 6:08pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics