Recommended Free Tools
A database licence may not count cores the way a virtual machine’s settings suggest. In a first-person DEV Community account, Serguey Shinder says his team discovered ten weeks into a migration that the applicable terms tied its core count to rented infrastructure. The database product, cloud provider and agreement are not identified, so the story is a warning to check the contract—not a universal rule about cloud licensing.
What happened in the migration
Shinder describes a migration already ten weeks underway when a consultant asked which licensing terms the team was relying on. According to his account, the relevant core count was determined by terms applying to the rented infrastructure, not simply by the virtual processors allocated to the virtual machine. The team then received a quotation for a licensing shortfall; Shinder did not disclose its amount. These details come from his account and are not independently verified. DEV Community
As an Amazon Associate I earn from qualifying purchases.
He says the team responded by reducing 31 database instances to nine, moving production onto hosts with a core count fixed in the contract, and moving two workloads to another database engine. The account does not name that engine, explain the workloads, or provide a cost comparison, so it cannot establish which change delivered savings or whether the same approach would suit another organization.
Shinder’s takeaway was: “In our own data centre the architecture decided the licence cost. In a rented one, the licence decides the architecture.” It captures the risk he describes, but the underlying licensing rule depends on the unnamed product and agreement.
#1 Best Overall
Does a cloud database licence count VM cores or host cores?
There is no general answer. The applicable product terms and contract determine the counting unit and the rights attached to a deployment. Depending on the product and hosting arrangement, licensing may turn on assigned virtual processors, physical cores, host configuration, or a particular license-included service. The migration account does not provide enough detail to decide which rule applied to that system.
Before choosing an architecture, establish the facts that control the terms:
Rank #2
- Product and edition: Identify the database software, edition, version, and whether the service is license-included or uses customer-provided licences.
- Entitlement and timing: Check how and when the licences were acquired, the agreement governing them, and whether Software Assurance or subscription rights are active.
- Hosting arrangement: Determine whether the deployment uses shared virtualized infrastructure, a dedicated host, or a managed service. Check which processor count the applicable terms use.
- Workload purpose: Separate production from development and test. The permitted edition and licensing route may differ.
- Architecture fit: Evaluate consolidation, dedicated placement, and a different database engine against application compatibility, operational needs, performance, and migration risk.
Why vendor-specific terms matter
Microsoft SQL Server
Microsoft lists SQL Server among products that may qualify for License Mobility through Software Assurance. Its guidance says active Software Assurance is required on all eligible-product licences, and instructs customers to check eligibility against current Product Terms. When deploying with an Authorized Mobility Partner, Microsoft also requires a verification form. For VMs on shared hardware, the guidance requires the VMs to be dedicated to a single customer. These are Microsoft-specific conditions, not evidence about the unnamed database in Shinder’s story. Microsoft License Mobility guidance
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Microsoft says its updated Listed Provider outsourcing policy took effect October 1, 2019. Its FAQ describes different treatment for SQL Server licences acquired before and on or after that date. For licences acquired on or after the effective date, use on Listed Providers’ dedicated hosted cloud services generally requires Software Assurance or equivalent subscription rights and License Mobility, unless the customer uses a license-included option. The FAQ also says unlimited virtualization rights do not apply to post-date SQL Server licences on those hosted services. Pre-date perpetual licences are addressed under the Product Terms in effect when they were acquired. The exact agreement and current terms must govern any deployment. Microsoft FAQ on the Listed Provider policy
SQL Server on AWS
AWS documents both license-included SQL Server instances and bring-your-own-license (BYOL) routes on EC2. Its guidance says requirements vary with instance type, SQL Server version, licensing model, and licence status. Active Software Assurance can enable License Mobility to shared-tenant EC2. Some deployments without Software Assurance on EC2 Dedicated Hosts require qualifying licences acquired before October 1, 2019, or true-ups under an earlier active Enterprise Enrollment. AWS also publishes Dedicated Host physical-core counts for licensing calculations. Confirm the current AWS guidance and the actual Microsoft agreement before choosing a route. AWS SQL Server licensing guidance
Oracle as a counterexample
Oracle’s cloud licensing policy illustrates why one vendor’s processor rules cannot be generalized to another. The cited policy addresses specified AWS EC2/RDS and Azure environments, counts maximum available vCPUs using its stated ratios, and says its Core Factor Table does not apply there. Oracle labels the document educational, non-contractual, and subject to change; it says the policy was in effect as of December 1, 2021. That date makes it especially important to verify current Oracle policy before relying on it. Shinder’s account does not identify Oracle as the vendor. Oracle cloud licensing policy PDF
Rank #4
- HP ProLiant DL360 G7 8B Server
- 2x X5650 2.66GHz 12-Cores Total
- 32GB RAM / 8x 146GB 10K 2.5in SAS Hard Drives
- P410 w/ 512MB
Review licensing before migration design is locked
A licensing review is most useful while deployment options are still open. Bring the proposed host and VM layout, workload inventory, product versions and editions, acquisition records, and governing agreements to the vendor, reseller, or a qualified licensing adviser. Ask for the counting method and applicable rights in writing, including how development and test environments are treated.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesThen compare the compliant choices on both licensing and technical grounds: consolidating duplicate instances, using a dedicated host, choosing a license-included service, or moving a workload to another engine. Shinder reports using several of these architectural levers, but his account does not identify the product or prove that any one choice is generally cheaper. A design that fits one contract may be wrong for another.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
