Skip to main content
License-included SQL Server Standard and Enterprise on RDS include the SQL Server license in the hourly price. SQL Server Developer Edition has the same features, is licensed for development and test only, and is priced well below them. nOps finds Standard and Enterprise instances that are marked as non-production and estimates the saving at the Developer Edition list price for the same instance class.

Why it matters

The license is most of the hourly price of a SQL Server instance, and development and test copies of production databases often carry the same edition.

How nOps finds it

nOps reads the last 7 days of on-demand RDS SQL Server Standard and Enterprise billing. An instance is flagged when nOps classifies its environment as non-production (dev, test, qa, staging, sandbox, uat, preprod or demo) and its name does not say production. The saving is the on-demand cost, scaled to a month, times the difference between the current and Developer Edition list prices for the same instance class and region. Instances not running in the last 2 days, instances mostly covered by Reserved Instances or credits, and savings under $5 a month are left out.

Before you start

Confirm the database is used only for development or testing. You need SQL Server Developer Edition installation media.

How to implement

  1. Confirm the instance is not production and serves no production users.
  2. Set up RDS for SQL Server Developer Edition in the region, which uses installation media you provide (see the RDS user guide for Developer Edition).
  3. Create a new Developer Edition instance of the same class.
  4. Move the databases, for example with native backup to S3 and restore.
  5. Point applications at the new instance, then delete the old one once nothing uses it.

Risks and considerations

  • Developer Edition is licensed for development and test only. Running production on it breaks the license terms.
  • The edition is not changed in place: you migrate to a new instance, so plan for a cutover.
  • To roll back, keep the old instance until the new one is confirmed working.

FAQs

From the environment nOps assigns to the account or resource. If the instance name says production, nOps leaves it out even when the environment says otherwise.