In my case I chose ‘Microsoft Windows Server 2019 with SQL Server 2017 Standard – ami-09ee4321c0e1218c3’. The solution was to create a new EC2 instance from a AWS Marketplace AMI that we would like to be billed for. The risk of reimplementation on a new EC2 instance and missing configuration was perceived to be high impact. The only concern our customer had with all the above approaches was that there was technical configuration on the source server that wasn’t well understand.
Leverage SQL Server native tooling between an on-premises Windows SQL Server to AWS EC2 Instance provisioned from a Marketplace AMI which includes SQL licensing.Leverage the AWS Database Migration Service (DMS) to migrate on-premises Windows SQL Server to AWS EC2 Instance provisioned from a Marketplace AMI which includes SQL licensing.Leverage the AWS Database Migration Service (DMS) to migrate on-premises Windows SQL Server to a Relation Database Services (RDS).There are a lots of options for migrating SQL Server to AWS, so we weren’t without choices. ((Invoke-WebRequest ).Content | ConvertFrom-Json).billingProducts If we review a migrated instance where ‘license-included’ was selected during launch, using Powershell on instance itself we see only a singular ‘BillingProduct = bp-6ba54002’ for Windows: This defines whether the launched test or cutover instance will include the license for the operating system (License-included), or if the licensing will be based on that of the migrated server (BYOL: Bring Your Own License).
We can see all we have is OS licence options available to toggle between license-included and BYOL.Ĭhoose whether you want to Bring Your Own Licenses (BYOL) from the source server into the Test or Cutover instance. In the Application Migration Service, under launch settings > Operating System Licensing. Rather then going to a license reseller and purchasing SQL Server it was preferred to have all the Windows OS and SQL Server software licensing to be payed through their AWS account. The customer was moving away from their current hosting platform where both licenses were covered under SPLA. While performing a lift and shift migration of Windows SQL Server using the AWS Application Migration Service I was challenged with wanting the newly migrated instance to have a Windows OS license ‘included’ but additionally the SQL Server Standard license billed to the account.
0 kommentar(er)
