Changing or Upgrading Your MS SQL Database Subscription
This guide explains how to upgrade your MS SQL database package or switch your subscription plan. Most users can now use the automated "Change subscription" tool. However, if you encounter errors or specifically wish to move your database to a different server, a manual migration procedure is also provided.
Important Considerations Before You Begin
- Resource Limits: Before switching plans via the automated tool, you must ensure that your current Database and Log sizes are less than or equal to the limits of the new package you are selecting.
- Purchase Required: You must have a valid MS SQL package (or a hosting package that includes MS SQL) purchased and available in your account.
- Downtime and DNS:
- Automated Method: Databases are typically not moved to another server during a subscription change. Therefore, there is usually no DNS replication delay.
- Manual Method: If you follow the manual migration steps to move to a new server, you may experience approximately 1 hour of downtime due to DNS propagation.
Method 1: Automatic Subscription Change (Recommended)
Use this method to upgrade or change your plan instantly without moving servers.
- Navigate to Database Properties
- In the control panel, navigate to the Databases section.
- Click on the name of the database you wish to upgrade.
- Initiate Subscription Change
- Locate and click the Change subscription button.
- A dialog box will appear displaying your available database plans.
- Select and Confirm
- Select the new package you purchased.
- Confirm the action. The update is generally immediate.
Method 2: Manual Migration (Moving Servers)
If you encounter an error with the automatic method, or if you specifically intend to move your database to a new server (e.g., moving from an unstable Express version to a paid non-Express instance on a different node), follow these steps.
- Backup Your Database
- Navigate to your current database properties in the control panel.
- Perform a full backup of the database.
- Delete the Old Database
- If you intend to use the exact same database name for the new plan, you must delete the existing database first.
- Crucial: When deleting, ensure you do not delete the backup location/files, so your data remains safe.
- Create the New Database
- Create a new database using your paid package.
- We recommend choosing a non-Express version of MS SQL, as Express versions are often shared with free hosting and can be less stable.
- Restore From Backup
- In the new database properties, restore the database using the backup file you created in Step 1.
Note for Manual Migration: The database will be available instantly after the restore, but due to DNS replication delay regarding the new server address, you may experience downtime of up to 1 hour. If you need to access it immediately, you may use the direct IP address provided in the database properties.