Follow along with RIM's guidelines here and things should go smoothly.
I've done this move several times, and downtime is very minimal. In my case,
the users didn't even know it happened. (or they were just quiet about it!)
Check the docs. There are specific things you must do on the SQL server
(including some scripts which modify things outside the BES DB.) Simply
moving the database won't work.
On Mon, Dec 14, 2009 at 8:41 AM, Gargano, Steve sgarg...@archerlaw.comwrote:
For those of you who have moved their
In our case, the DB move went very smoothly. However, as Michael and Rich have
both asserted to, the new SQL server needs to have the BES scheme updated in
its master tables or something like that. To get around that we simply allowed
BES to create a new database on the destination SQL server,
I agree with Rich Don. You've outgrown MSDE long ago.
You'd want to have the SQL database/server in the same data center. If it's in
a remote data center, then you would ideally want to have a redundant network
path to get to it. In case of an outage, the BES can operate ok without being
.
From: bes-admins-boun...@dataoutages.com
[mailto:bes-admins-boun...@dataoutages.com] On Behalf Of Vance, Trevor K
Sent: Thursday, July 16, 2009 12:39 PM
To: A list for BES Admin's to discuss issues, etc.
Subject: Re: [Bes-admins] SQL Database
I agree with Rich Don. You've outgrown MSDE
