views:

170

answers:

2

Question: Is it possible to stop SSMS from monitoring the service status of registered servers?

Details: SSMS 2008 monitors the service status of every registered server. From what I have seen it seems to reach out to every registered server every minute or so to check it's status, in my case that is over 100 servers. This process has raised issues with our Security and Network departments. Network identified it initially as suspicious traffic due to the fact that it appeard as an unknown utility was scanning the network for SQL Servers. Security was concerned because the Security Event Logs on each server are being filled up with my logon events.

I have looked all over for a setting but can't seem to find one. Am I missing it somewhere?

TIA, Brian

A: 

Since it doesn't appear that there's any way to stop these status checks by SSMS, can you focus on helping them to see their harmlessness?

  1. Can the network group allow certain exceptions to this particular rule (pinging servers on port 1433) in their scanning software, which would allow you and your group to monitor SQL Server uptime? Even if you weren't using SSMS, this type of sweeping monitoring activity is pretty common, and you'll know the requests will only ever come from a handful of workstations.
  2. I don't think these SQL status checks generate any more events in the security log than any other activity, so maybe they were just concerned because it was something they weren't expecting. Could the security group be convinced that these events aren't dangerous, again as long as they're coming from certain approved workstations?

If neither of these is an option (or even if it is), you could help mitigate the problem by not connecting to all your SQL servers at once. Maybe just connect to the ones you need at the time - it looks like loading the entire list actively connects to each of them, but just connecting to the ones you intend to use in that session might help reduce the number of network sessions open.

I hope this helps - if it doesn't, or you've got some additional input that might help find a workaround, please post it!

rwmnau
Thanks for the reply. We've already done #1 and the issue with the event log isn't that the entries are there it's that there are about 1000+ a day.I'm not connecting to all my servers at once. I have entries for them in Registered Servers, basically shortcuts to connect with all settings saved. I usually only connect to a few at a time and close the connections when I am not using them.
BrianD
+1  A: 

I finally found an answer!!

While it is not possible (at least that I've found) to stop SSMS from checking the service status of registered servers it is possible to change the interval at which it checks it.

The short version is to create the following registry keys (DWORD):

(SQL Server 2008) HKLM\Software\Microsoft\Microsoft SQL Server\100\Tools\Shell | PollingInterval = 600 (decimal)

(SQL Server 2005) HKLM\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell | PollingInterval = 600 (decimal)

This will make SSMS connect automatically every minute instead of every few seconds.

See this MS Connect Post for details.

BrianD