BlackBerry Forums Support Community - View Single Post - Upgrading from SQL Express to SQL 2008 R2

loweredxtreme · 11-02-2010, 11:59 AM

Seeking some advise from other BES admins/experts

Currently Running:
BES v5 with SQL Express running in Windows Server 2003 R2 with activated fail-over

Our organization is wanting to implement SQL 2008 Std R2 so we can take advantage of the databases mirroring as Blackberries are very important to our organization.

My superiors are very concerned about downtime and want to make it as minimal or none if possible.

Their solution is to deactivate the fail-over server and start from scratch, rebuild BES with SQL 2008 R2 and create a new database and then use the user transfer tool to switch users over, essentially turning the fail-over to production.

I personally DO NOT want to start over. I understand that the services must stop to mirror the database, but if I activate the fail-over server does that allow me safely to upgrade the SQL server on the production, point it to the established database without any downtime during the upgrade? Or must the I stop the services before the SQL upgrade?

Also, has anyone ever done this and run into any problems that cause damaging results?

I thank everyone in advance. Sorry so long.

11-02-2010, 11:59 AM	#1
loweredxtreme Knows Where the Search Button Is Join Date: Sep 2006 Location: California Model: 9630 Carrier: Verizon Posts: 33	Upgrading from SQL Express to SQL 2008 R2 Please Login to Remove! Seeking some advise from other BES admins/experts Currently Running: BES v5 with SQL Express running in Windows Server 2003 R2 with activated fail-over Our organization is wanting to implement SQL 2008 Std R2 so we can take advantage of the databases mirroring as Blackberries are very important to our organization. My superiors are very concerned about downtime and want to make it as minimal or none if possible. Their solution is to deactivate the fail-over server and start from scratch, rebuild BES with SQL 2008 R2 and create a new database and then use the user transfer tool to switch users over, essentially turning the fail-over to production. I personally DO NOT want to start over. I understand that the services must stop to mirror the database, but if I activate the fail-over server does that allow me safely to upgrade the SQL server on the production, point it to the established database without any downtime during the upgrade? Or must the I stop the services before the SQL upgrade? Also, has anyone ever done this and run into any problems that cause damaging results? I thank everyone in advance. Sorry so long.
Offline