Hi Chris,
Could you tell me if the "update time" is configurable? I'm having a problem where my primary polling engine is failing over for reason(s) unknown. I suspect root cause is that my "update time" is too short for the size of the database (about 3600 objects). I'm theorizing that my pollers are sending the updates to my SQL box in a timely manner, but the SQL box may be queueing them just long enough for the update interval time to expire thus causing my hot-standby to take over. Interestingly, the problem goes away after I restart the Solarwinds (SW) services on all three SW servers (primary, secondary and standby) and the SQL service on the SQL box. However, the problem always comes back five to seven days afterwards, thus making me think that I may also have some kind of memory leak on the SQL box (although I've yet to see any problems that way after checking the SQL box).
I thank you very much for your time and assistance.