We have R2-CU5, but we don't have the registry entries for "DALInitiateClearPool" and "DALInitiateClearPoolSeconds" in place. We had two outages of the SQL Server due to reboots after patching via SCCM. One lasted 2.5 mins and another lasted 8 mins. I think this was our problem. I'll make the changes in our lab and then test them. Thanks - the problem of having an open mind is, there is always someone trying to put something in it.

Let us know if it doesn't fix it but it should do the trick. Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Environment: SCOM 2007 R2 running on Windows Server 2008 R2 Standard (RMS Server) SQL 2008 SP2 Standard X64 on Windows Server 2008 R2 Standard (Separate SQL server) Normally we get alerts sent to our mobile phones. However, whenever the SQL server is rebooted, all alerts stop until we restart the "System Center Data Access" and "System Center Management" services on the RMS server. Is this normal behaviour? I would think that once the SQL server comes back, the RMS server should be able to reconnect automatically.- the problem of having an open mind is, there is always someone trying to put something in it.

What Cumulative Update are you using? http://blogs.technet.com/b/kevinholman/archive/2011/02/07/a-new-feature-in-r2-cu4-reconnecting-to-sql-server-after-a-sql-outage.aspx Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/