This is because the database table "LatestNumericCounterData" has grown excessively large and is slowing the queries generated by clicking on the ellipsis button associated with Server filters.
You need to determine how big the table is and how many days worth of data is retaining. To find out how big the table is, perform the following steps:
1. In SQL Server Enterprise Manager, navigate to the SOE database in the tree view, and click on Tables.
2. In the action pane, right click on the LatestNumericCounterValues table and select Properties.
3. Note the number of rows as displayed in the Table Properties box.
To find out how many days worth of data are being retained you can use the SOE GUI, or you can find out directly from the database by the following procedure
1. Locate the table T_DataRetentionSettings and right-click on it.
2. Select the Open Table | Return all rows option.
3. Note the numeric value.
The default value for the number of days of data that is retained is 30. If it's currently set to a higher value, then it should be reduced to 30. If it currently is set to 30, it could be lowered even more to increase performance. Once (or if) the number of days is lowered, manually run the SQL job that truncates the table by executing the following commands in SQL Query Analyzer:
USE SOE; EXEC spu_PurgeHistoricalData;
This will allow you to immediately verify that truncating the table has resolved the timeout issue. Otherwise, you can lower the number of days and wait until tomorrow to check, since the PurgeHistoricalData job should run automatically at some point before then.