When you want to upgrade your SQL database to a newer version, we can migrate the database for you or you can do it yourself. Which option is best for you depends on your needs.
When we migrate a database for you:
- We recommend that you first put your site into maintenance mode
- We will set the database to read only (to insure that no new data can be entered during migration) and make a backup
- Then we will create a new database on the SQL version of your choice and restore the database from the backup
- We will provide you with the new login information (database server name, login, etc.)
- You will then update your application connection string to point to the new database server
- We will delete the old database, and the process will be complete
When you migrate a database yourself, you have more control over the process of course, and you can keep both the old and new databases online concurrently during the migration, which can be beneficial in certain circumstances.
The main drawback to self-migration is the need to order the new database, so you incur an additional cost during migration. Though you can get a credit applied to your account for the time remaining on the old database when you cancel it, you still essentially pay for two databases while both are active.
Typical steps of a self-migration:
- Order a new database on the SQL version of your choice
- Make your old database read only (to insure that no new data can be entered during migration)
- Make a backup of the old database and restore it to the new database
- Update your application connection string to point to the new database server
- Contact the billing department to cancel your old database
We are still here to assist you with any help you need, even during a self-migration.
Databases from SQL 2008 and older cannot be directly restored to newer versions of SQL server. And so for those versions in particular we recommend having Support perform the restore / upgrade.