Topic lessonTopic: RDS and SQL Server: management, connections and deployment
Estimate RDS costs: SQL Server charges, licensing and stopped instances
An RDS estimate needs aligned instance, storage, backup, network and licensing assumptions. Use SQL Server to compare deployment choices and understand costs that can remain after stopping. All amounts in the worked example are teaching values, not AWS rates.
Organize estimate assumptions and charge categories without treating a low rate, stopping or license mobility as proof of the total.
For readers familiar with RDS responsibilities and storage. Read pricing assumptions and a fictional estimate; no purchase, commitment or database creation is performed.
Separate the components of an estimate
- Align assumptions → Add charge categoriesMatch rates and usage under the same conditions
- Add charge categories → Compare equal scopeReport totals together with exclusions
- Align assumptions
- Specify Region, edition, deployment, period and workload.
- Add charge categories
- Include storage and networking beyond compute.
- Compare equal scope
- Record inclusions and exclusions before comparing.
| Category | What changes it? | A common gap |
|---|---|---|
| DB instance and licensing | Class, hours, deployment, version/edition and pricing/license model | License rights being included is distinct from bundled or separated billing components |
| Storage and I/O performance | Provisioned capacity, storage type, IOPS/throughput and other settings | Check allocated capacity and performance, not only bytes of stored data |
| Backup-related storage | Retained amount, retention and extra copies | Include retained copies that outlive the database |
| Network and adjacent features | Transfer direction, path, Regions and enabled features | Check other costs such as DMS, logs and public IPv4 |
Fix comparable assumptions before comparing rates
| Assumption | Record |
|---|---|
| Location and period | Region, estimate date, currency, operating hours, billing units and tax treatment |
| Database and deployment | Engine version, edition, class, Single-AZ/Multi-AZ and replicas |
| Storage and load | Provisioned capacity, required IOPS, retained backups, transfer volume and path |
| Purchase and license model | On-Demand/commitment terms, LI/BYOM and existing agreement scope |
| Comparison boundary | RDS only, or migration, logging and operations too; list exclusions |
Separate license inclusion, mobility and infrastructure charges
License Included (LI) includes the applicable SQL Server license under the AWS offering. Current pricing distinguishes bundled and unbundled compute/licensing components. LI does not always mean a single billing line.
Bring Your Own Media (BYOM) uses your qualifying SQL Server licenses. Check Software Assurance and edition eligibility. Existing licenses do not remove RDS infrastructure, Windows, storage or transfer costs. Developer eligibility does not authorize production use.
Example E1: add beyond 100 to reach 135
The following USD amounts come from a fictional teaching quote, not AWS rates or a standard deployment. Add four categories under one stipulated period and configuration. Tax, migration, logs, public IPv4 and other items are excluded; this is not a prediction of a complete invoice.
| Category | Teaching amount |
|---|---|
| Compute plus chosen license terms | 100 USD |
| Storage | 20 USD |
| Backup | 5 USD |
| Transfer | 10 USD |
| Total for these four items | 135 USD |
100 + 20 + 5 + 10 = 135. Looking only at 100 misses another 35 even within this limited quote. Subtracting 100 identifies the other categories; it does not predict a post-stop bill of 35. Duration, usage and contract terms must be reassessed after stopping.
Stopping does not remove storage and contract checks
| Check | Decision |
|---|---|
| Can it stop? | SQL Server Multi-AZ, databases with replicas and replicas themselves have restrictions |
| Stopped DB instance hours | The documented stopped state excludes DB instance-hour charges; do not conflate stopping transitions or contract obligations |
| Retained resources | Provisioned storage/IOPS, backups and applicable public IPv4 can still incur charges |
| Duration | Automatic restart after at most seven days; stopping is not indefinite free storage |
Keep an estimate that can be compared again
- Establish version, edition, performance, availability and read requirements first.
- Record Region and date, then align inputs in official pricing or Calculator.
- List compute/license terms, storage, backups, network and adjacent features.
- When changing deployment or purchasing models, compare totals and exclusions.
- After validation, reconcile actual usage and line items; separately manage budget notifications and cleanup.
Check estimate decisions
Choose an option to see the result and explanation.
Check, then explain in your own words
- Write assumptions and included/excluded scope.
- Match usage and rates by category.
- Separate the effects of stopping and licensing choices.
- Explain the total and omitted items.
Check your understanding: Is E1 minus 100, or 35, the actual bill after stopping?
No. It only sums the other categories in the supplied quote.
A real bill requires reassessing time, usage, deployment and contract terms.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- AWS: RDS for SQL Server pricingChecked:
Scope and conditionsCurrent LI/BYOM, bundled/unbundled and commitment options; compare equivalent conditions without fixed-price/free guarantees.
Used in this lessonSeparate the components of an estimate Fix comparable assumptions before comparing rates Separate license inclusion, mobility and infrastructure charges Stopping does not remove storage and contract checks
- AWS: SQL Server licensing on RDSChecked:
Scope and conditionsLI/BYOM rights versus infrastructure charges; Developer is for non-production use.
Used in this lessonSeparate the components of an estimate Separate license inclusion, mobility and infrastructure charges
Scope and conditionsStorage-related charges while stopped; seven-day restart and SQL Server Multi-AZ/replica stop restrictions.
Used in this lessonSeparate the components of an estimate Stopping does not remove storage and contract checks