Upgrading MSDE to SQL 2005
One of my clients has been running Blackberry with MSDE and we're thinking about upgrading from MSDE to SQL Server 2005 on that machine. The upgrade advisor specficially said that an upgrade will break the Blackberry database, so I'm wondering what the best option for this is? We're thinking we'll have to uninstall everything and just start fresh with SQL Server 2005 as the database, but won't that require re-activating all the users?
Follow this article to backup and restore the database:
BlackBerry Search Results
Here are the steps I would follow:
1. Backup the db and move the besmgmt.mdf and besmgmt_log.ldf files to a safe location. This will require you to stop the MSSQLSERVER service
2. Uninstall MSDE
3. Install SQL 2005
4. Assign the permission for SQL 2005
5. Create the blank db using createdb.exe
6. Restore your backerd up over the newly created BESMgmt db
7. Point the BES to use the database on the new SQL Server 2005 instance
All the backup/restore/createdb.exe steps are in the KB above. Feel free to ask any questions.
I just did the migration from MSDE to SQL Server 2005 2 days ago:
Our server is a BES 4.0.6 for IBM Lotus Domino. I did the following steps :
- I did a backup of MSDE Database.
- Stoped MSDE & blackberry services and copied BESMgmt.mdf and BESMgmt.ldf files (only those two files), (I did not uninstall MSDE, just disabled the service)
- Installed SQL2005 and created a new db instance.
- copied BESMgmt.mdf and BESMgmt.ldf to the data directory of my SQL2005 data directory
- From the SQL 2005 studio manager, attached the mdf file, it has automatically referenced the .ldf file as well.
- Looked at the Blackberry services, some services starts with a different user account... (mine was LOCALSYSTEM for most of the BB services except BBDispatcher that was running under the local Administrator account, so I had to assign dbowner & dbcreator rights in the SQL db for this user.
- I ran Blackberry server config and pointed the db to the new instance.
- I ran BB manager and did the same.
Now I came accross a problem with the blackberry dispatcher service that wouldn't start with service specific error 5608 :
To fix that I ran Blackberry server config again and created a 2nd db (in the same SQL2005 instance), for example BESmgmt2, i clicked next, it asked for srp id... I clicked cancel.
I relauched Blackberry server config and pointed it back to the original db.
Pb solved and migration finished.
So far I didn't had any user reporting that their Blackberry is not working, no need to reactivate any devices.
So this is the quick and maybe-not-so-dirty way to do it, :razz:
I found the migration documentation provided by RIM a bit confusing as I'm by no ways a db admin. Hope this helps.
Most of the BES services should be starting as your BESAdmin account, not localsystem.
Only the MDS Connection Service, MDS Apache Tomcat and the BlackBerry Alert start as localsystem as per RIM documentation. This is by default and should not be changed.
Just thought I would mention that.
Also, your 5608 error would have been avoided by creating a blank db first using createdb.exe. Not using that utility leaves entries missing in the sysmessages table that the service needs on startup.
The article from RIM is not difficult to follow. It's a step by step guide that has all the necessary steps to complete the move.
Thanks for the info. I need to do this fairly soon. Question: do the blackberry services need to be stopped at all during this process? Just trying to figure out downtime for our users.
You would stop your services if you wanted to copy the BB database files only. When you use the BlackBerry Server Configuration utility to change the database the services are stopped and started automatically as part of the process.
The KB posted in the link has all the steps you need to follow. Read through it and plan your database move.
|All times are GMT -5. The time now is 03:37 AM.|
Powered by vBulletin® Version 3.6.12
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.