INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Organize estimate assumptions and charge categories without treating a low rate, stopping or license mobility as proof of the total.

Prerequisite

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

From aligned assumptions to charge categories and comparison
From aligned assumptions to charge categories and comparison1: Align assumptions — Match rates and usage under the same conditions — Add charge categories. 2: Add charge categories — Report totals together with exclusions — Compare equal scope12Align assumptionsAdd chargecategoriesCompare equal scopeFrom aligned assumptions to charge categories and comparison1: Align assumptions — Match rates and usage under the same conditions — Add charge categories. 2: Add charge categories — Report totals together with exclusions — Compare equal scope12AlignassumptionsAdd chargecategoriesCompare equalscope
  1. Align assumptions → Add charge categoriesMatch rates and usage under the same conditions
  2. 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.
Charge categories to check for SQL Server
CategoryWhat changes it?A common gap
DB instance and licensingClass, hours, deployment, version/edition and pricing/license modelLicense rights being included is distinct from bundled or separated billing components
Storage and I/O performanceProvisioned capacity, storage type, IOPS/throughput and other settingsCheck allocated capacity and performance, not only bytes of stored data
Backup-related storageRetained amount, retention and extra copiesInclude retained copies that outlive the database
Network and adjacent featuresTransfer direction, path, Regions and enabled featuresCheck other costs such as DMS, logs and public IPv4

Fix comparable assumptions before comparing rates

Equal-looking amounts can cover different scopes
AssumptionRecord
Location and periodRegion, estimate date, currency, operating hours, billing units and tax treatment
Database and deploymentEngine version, edition, class, Single-AZ/Multi-AZ and replicas
Storage and loadProvisioned capacity, required IOPS, retained backups, transfer volume and path
Purchase and license modelOn-Demand/commitment terms, LI/BYOM and existing agreement scope
Comparison boundaryRDS 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.

Sum the four supplied quote items
CategoryTeaching amount
Compute plus chosen license terms100 USD
Storage20 USD
Backup5 USD
Transfer10 USD
Total for these four items135 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

Separate stop eligibility from charges while stopped
CheckDecision
Can it stop?SQL Server Multi-AZ, databases with replicas and replicas themselves have restrictions
Stopped DB instance hoursThe documented stopped state excludes DB instance-hour charges; do not conflate stopping transitions or contract obligations
Retained resourcesProvisioned storage/IOPS, backups and applicable public IPv4 can still incur charges
DurationAutomatic restart after at most seven days; stopping is not indefinite free storage

Keep an estimate that can be compared again

  1. Establish version, edition, performance, availability and read requirements first.
  2. Record Region and date, then align inputs in official pricing or Calculator.
  3. List compute/license terms, storage, backups, network and adjacent features.
  4. When changing deployment or purchasing models, compare totals and exclusions.
  5. 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.

What is the sum of E1: 100, 20, 5 and 10 USD?
Read the answer and reason

Answer: 135 USD for the four supplied categories. · Add all four; this is not a real AWS price including excluded costs.

Does stopping make every cost, including storage and backup, zero?
Read the answer and reason

Answer: No; check stop eligibility and retained charge categories. · Separate stopped instance hours from storage, IOPS, backups and other charges.

You own a SQL Server license. Does BYOM also make AWS compute and storage free?
Read the answer and reason

Answer: No; usage rights and infrastructure charges are separate. · Even eligible licenses leave AWS infrastructure costs to evaluate.

Choose between a Single-AZ monthly total and a Multi-AZ rate with unspecified conditions?
Read the answer and reason

Answer: No; align period, deployment, licensing and charge scope. · State workload requirements and included/excluded charges.

Check, then explain in your own words

  1. Write assumptions and included/excluded scope.
  2. Match usage and rates by category.
  3. Separate the effects of stopping and licensing choices.
  4. 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.