Recently I see a lot of posts on Windows Azure Forum related to deployments cycling between Initializing, Busy and Stopping states. In this post I would like to summarize the most common reasons why is this happening. Here they are:
Copying Databases in SQL Azure (#copydb #azure)
Windows AzureMicrosoft SQL Azure Database is the relational database service on the Windows Azure platform. Once you have created a database in SQL Azure, you can back up that database by copying it to a new database in SQL Azure. The new database that is created from the copy process is a regular database once the copy is complete: fully functioning and independent of the source database. In addition, the new database will have the same edition and maximum size as the source database.
Overview
The database copy feature enables many of the back-up scenarios you may be familiar with for on-premises databases:
- Application data back up: Copy the application database to a new database in order to help protect it from user and application errors. Recover the application database state by renaming the new database with the application database name. Alternatively, recover a specific subset of data from the new database by use of Transact-SQL queries.
- Application development and testing: Copy the production database to a new database that can be used for development and testing.
- Application upgrade: Copy the application database to a new database before major application updates. If a mistake is made during the upgrade, recover the earlier database state by renaming the new database to the application database name.
Nice!
