Do you have RIMESP.DLL configured on your SQL server?
Reason I ask... We have 4000 users x 6 BES servers and 1 SQL server. A 2nd SQL server in a remote location is a logshipping recipient for a DR replica.
We reboot our BES and SQL weekly in the wee hours of sunday morning. We used to have a problem where our SQL server would get very slow and painful, also after about a week, log shipping would fail.
At one point it got so bad we had to reboot every few days, and our BES console was painfully slow. (see my thread on this forum about SQL performance)
On Microsoft SQL support's recommendation, we removed RIMESP.DLL from our SQL2000 server. end result - the sql server CPU performance has dropped by some 40%, memory leaks are gone, BES console is alot faster for user lookups, and our whole environment seems to be behaving better.
we are still doing the weekly reboots, but i'm beginning to wonder why, i no longer think we need it.
my point - if you are questioning SQL performance, and need to reboot periodically to free up various system resources (mainly memory) consider getting rid of that crazy dll.
Originally Posted by RadHaz75
Does anyone reboot their BES servers on a routine basis?
We have 10,000 users on 15 servers and reboot them all in a staggered 15 minute manner around 3 AM. We did this given guidance from RIM a while ago because the SQL server couldn't process the amount of information being passed to it in an efficient manner and basically the servers would start to crash after a few days, so rebooting the servers at night allowed it to catch up with itself. The SQL server is a powerful box, but we were sitting there with our DBA and he was watching the commands being run and said he's never seen so much data being passed so fast and he's been a DBA for like 15 years.
Guess I should add we are running 4.1.5 with Exchange 2003 and SQL 2000