For more information, see Deploy projects to Microsoft Azure.
PREREQUISITES: During the upgrade, you must temporarily decrease your role instance count to a single instance.
NOTE: If the project you want to upgrade is not in the list of projects of the project manager, you must add it. For more information, see Work with Sitefinity CMS Project Manager.
RECOMMENDATION: Because this project is configured to connect to your production Azure SQL database and using it locally, you can modify it, we recommend either to avoid using it locally, or to temporarily change the database connection string.
NOTE: If you have other means to ensure no data is changed or the changes after the backup can be discarded in case of failure and database restore, you can leave the production environment online.
For this purpose, you can use Microsoft SQL Server Management Studio 2008 R2 or use an instance of database manager co-located in every Azure SQL datacenter. You can launch it from the Management Portal » Databases » <Your Subscription> » <Your Server> » master » Manage.
NOTE: In both cases, you must login to the master database, because this is a requirement for the special purpose statement.
CREATE DATABASE <copy> AS COPY OF <original>
Replace <copy> with the name of the backup copy database and <original> with the production database’s name.
The above statement only initiates the copying process.
SELECT name, state_desc FROM sys.databases
Execute the statement as many times as needed, until you see that the <copy> database is in ONLINE state.
NOTE: The new database created from the copy process is transactionally consistent with the source database at the point in time when the copy completes. This means, that the role instances, which are running against this database, do not have to be stopped. However, if, for whatever reason, a data loss is experienced during the upgrade of the production database, the copy that will be restored will not have the data that was stored in the source database, after the copying process is complete. For this reason, you may prefer to plan some downtime during the upgrade.
RECOMMENDATION: The new Sitefinity CMS deployment will perform an online upgrade of the live production database on the first request to the application. We recommend you to request the site to force the upgrade and ensure there are no problems with the upgrade.
<Instances count="3" />
NOTE: Microsoft Azure creates and starts new instances to satisfy the required count. This is a time consuming process. During this time, the single instance is still available.
The same applies for the database copy.
ALTER DATABASE <old_name> MODIFY NAME = <new_name>
NOTE: To download an Azure SQL database, see Export an Azure SQL database to a BACPAC file.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2020 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity