Datavail: Migrating SQL Server to AWS – FastPass

Datavail 0 views 25 slides Oct 09, 2025
Slide 1
Slide 1 of 25
Slide 1
1
Slide 2
2
Slide 3
3
Slide 4
4
Slide 5
5
Slide 6
6
Slide 7
7
Slide 8
8
Slide 9
9
Slide 10
10
Slide 11
11
Slide 12
12
Slide 13
13
Slide 14
14
Slide 15
15
Slide 16
16
Slide 17
17
Slide 18
18
Slide 19
19
Slide 20
20
Slide 21
21
Slide 22
22
Slide 23
23
Slide 24
24
Slide 25
25

About This Presentation

Migrating SQL Server to AWS – FastPass
Are you planning to migrate your SQL Server environment to AWS but unsure where to start? This comprehensive presentation by JP Chen, Senior Director and Global Practice Leader of SQL Server Services at Datavail, provides a clear roadmap for a successful migr...


Slide Content

Datavail: Fast pass for migrating SQL Server to AWS JP Chen Senior Director of SQL Practice Datavail

J JP Chen Senior Director of SQL Practice, Datavail Enterprise SQL Support As a DBA, DBA Team Manager, and then Director, JP brings a wealth of technical knowledge and hands-on experience to every project. AWS Expertise and Cloud Migration 9+ years of AWS expertise. Helping 100+ customers with their cloud migrations to Amazon EC2 and Amazon RDS for SQL Server. SQL Server Blogs and Whitepapers Eager to share his knowledge with the larger SQL Server community, JP is an avid blogger and author, posting regular content on Datavail.com. www.datavail.com 2

Agenda Why Migrate SQL Server to AWS? Quick Comparison of On-Premises, IaaS, and PaaS SQL Server Deployment Options in AWS – IaaS vs PaaS AWS Essential Services for SQL DBAs Migrating to Amazon RDS for SQL Server (PaaS) AWS Database Migration Service (AWS DMS) Migrating to SQL Server on Amazon EC2 (IaaS) Sample Case Study – HADR, Migration, and Modernization DBA Responsibilities in the Cloud – HADR, Migration, and Modernization

Target Audience, Prerequisites, and Q&A Level: 100 to 200 Prerequisites: Cloud experience helpful but not required Q&A: As we have limited time for this quick presentation, we will do a Q&A at the end.

About Datavail Databases Windows Workloads Open-Source Workloads Oracle Workloads 100+ Cloud SAs and Engineers 16+ Years Database Services 700+ Customers 8+ Years Cloud Experience 200,000+ Databases Managed 150+ Cloud Migrations Expertise Experience Outcome Data Integration and Analytics AWS Partner

Why Migrate SQL Server to AWS? Reduce CapEx and OpEx Elasticity Speed of provisioning Automation of HA/DR and many other maintenance tasks Large and efficient cloud

On-Premises Example: Use your own server in your network with upfront costs; you are responsible for maintenance and uptime. Infrastructure as a Service (IaaS) Example: Use an Amazon EC2 instance (VM). Less upfront cost, as you are leasing it. You can customize the server to your exact requirements. You are still responsible for updates, security, uptime, and maintenance. Platform as a Service (PaaS) Example: Use Amazon RDS from AWS. Minimal upfront cost, and you do not need to be concerned about the maintenance of the machine. Quick Comparison of On-Premises, IaaS, and PaaS On-Premises Servers Storage Networking Virtualization OS Middleware Runtime Applications Data IaaS Servers Storage Networking Virtualization OS Middleware Runtime Applications Data PaaS Servers Storage Networking Virtualization OS Middleware Runtime Applications Data

Platform as a Service (PaaS) Amazon RDS for SQL Server Fully managed relational database service Choose this: If you don’t need to customize your environment. Amazon RDS Custom for SQL Server Released: Dec 1, 2021 Privileged access to the OS Choose this: If you want to customize the database, OS, and infrastructure. Infrastructure as a Service (IaaS) SQL Server on Amazon EC2 instances Exact match of your on-premises SQL Servers on virtual machines OS-level access and control SQL Server Deployment Options on AWS – IaaS vs PaaS

AWS Essential Services for SQL DBAs AWS Regions AWS Availability Zones (AZs) Amazon Simple Storage Service (S3) AWS Identity and Access Management (IAM) Availability Zone C Availability Zone A Availability Zone B

Creating Your Amazon RDS for SQL Server Instance – Checklist Edition: SQL Server Standard Edition Version: SQL Server 2019 15.00.4043.16.v1 Templates: Prod or Dev/Test DB instance identifier: rdsforsqldemo Master username: admin Master password: Xxxxxxxxx DB Instance Class: Standard classes (includes m classes); db.m5.large; 2 vCPUs; 8 GiB RAM; Network: 4,750 Mbps Storage: General Purpose (SSD); 20 GiB; For Production, choose Provision IOPS. Multi-AZ Deployment: Yes or No VPC: Default VPC Public access: Yes or No Security Group: Default Additional configuration: DB Parameter Groups (think sp_configure) and Option group (to be covered later)

Modify the Security Group to add inbound rules to allow MSSQL port 1433 Finding the connection information: Endpoint Port number Opening a connection in SSMS Copy and paste the endpoint in the server name Put comma(,) and then the port number Connecting to Your Amazon RDS for SQL Server Instance

Fastest way to migrate is to backup and restore databases RDS supports native restores of databases up to 16 TB. If your database can go offline, then use native backup and restore to migrate it to Amazon RDS. Else, use AWS Database Migration Service (AWS DMS). Migrating to Amazon RDS for SQL Server Using Backup and Restore https://docs.aws.amazon.com/AmazonRDS/latest/ UserGuide/SQLServer.Procedural.Importing.html

1. Create an AWS DMS replication instance. 2. Configure the source and target endpoints. 3. Create a database migration task. 4. Stop data replication during cut-time time. 5. Point your application to the Amazon RDS endpoints. AWS Database Migration Service (AWS DMS) https://docs.aws.amazon.com/dms/latest/userguide/CHAP_ReplicationInstance.VPC.html

AWS Snow Family AWS Snowcone: 14 TB AWS Snowball: 50 TB and 80 TB AWS Snowmobile: 100 PB Steps : Order it online from AWS Copy the data Ship it back to AWS Large migration?

Considerations Need full control, backups, replication, clustering, and options not available in Amazon RDS. Run SQL Server on Amazon EC2 instances (VMs) Planning Take a performance baseline of your on-premises instance Identify hardware, capacity, storage, and network requirements Determine the backup strategy and availability requirements Agree with your teams on the application migration and cutover strategy. Post-Migration Activities Run index and statistics maintenance jobs Enable database monitoring and alerting Perform query tuning, wait stats analysis, and tempdb optimization Capture performance baseline on a continual basis for benchmarking Migrating to SQL Server on Amazon EC2 (IaaS)

Sample Case Study – HADR, Migration, and Modernization Situation: On-premises environment and challenges Tasks: Enable HADR, increase performance, and move out of the old data center Action: Setup SQL Server Always-On Availability Group (AOAG) Result: HADR, performance, environments resemblance, and AWS Cloud environment

On-Premises Environment and Challenges Active/pass clustered SQL instances Real-time reporting for BI and analytics Production and non-production environments disparity Infrastructure modernization Data center lease is up at end of year

Enable HADR, Increase Performance, and Move Out of the Old Data Center Enable HADR Replace replication Increase performance Reduce environments disparity Migrate to the AWS Cloud

Baselining the On-premises Environment: Run PerfMon to capture the performance for a typical workload: memory, disk, CPU, and SQL Save the results for benchmarking purposes Planning for the migration: Instance type: vCPU, memory (GiB), instance storage (GiB), networking performance (Gbps), and Amazon EBS bandwidth (Mbps) AWS Region and AZs: Oregon Region with 3 AZs AWS Pricing Calculator: https://calculator.aws/#/ Team Sport: DBA, systems, network, dev, and PMO Luckily, we always have amazing teams to collaborate with us Set up and Migrate to SQL Server Always-On Availability Group (AOAG) on AWS

Install Windows Cluster Install standalone SQL Server on all 3 nodes Create a test database Enable Always-On Availability Groups for all nodes using SQL Server Configuration Manager Create an Availability Group (AG) Configure Read-Only-Routing Test failovers and Read-Only-Routing Configuring SQL AOAG - Overview

Availability Modes Synchronous-commit (HA) Asynchronous-commit (DR) Read-Only Routing List Primary replica: INSERTS, UPDATES, DELETES Secondary replica: Read-Only and Reporting. Instructions for the App and Dev Teams: Availability group listener. Example: SQLSRVCONN01 Connection string. Example: “Initial Catalog=DBName;ApplicationIntent=ReadOnly;MultiSubnetFailover=True” SQL AOAG High-Level Overview Diagram

HADR, Performance, Environments Resemblance, and AWS Cloud Environment HA DR Performance gain through Read-Only Routing Non-production environments provision through AMI AWS Cloud environment

DBA Responsibilities in the Cloud Category DBA Responsibility IaaS PaaS Software Installation and Maintenance Install and configure new SQL Server instances.    Ongoing updates and patches.    If new server is needed, transfer of data from existing system to new platform.   Database backup and Recovery Create backup plans to backup the databases.   Develop recovery plans and procedures to recover the databases in case of disaster.   Test and verify the recovery plans to meet business recovery objectives.   High Availability and Disaster Recovery (HADR) Plan, design, and implement high availability and disaster recovery (HADR) solutions based on business requirements; e.g. SQL AOAG, clustering, database mirroring, and log shipping.    Test and verify the HADR solutions on set schedules as per business requirements.  

DBA Responsibilities in the Cloud Category DBA Responsibility IaaS PaaS Performance Monitoring and Database Tuning Monitor databases for performance issues.   Tune the database based on application and usage.   Re-balance workloads across database servers based on monitoring.   Security and Authentication Implement best practices to minimize security risk.     Setup and grant employee and application access based on the principle of least privilege (PoLP).   Capacity Planning Workload (I/O) capacity planning.     Storage and disk space usage capacity planning.   Data Extract, Transformation, and Loading Import large volumes of data that have been extracted from multiple sources into a data warehouse or into a centralized repository.     Troubleshooting Quickly understand and respond to problems when they occur and restore data or correct issues to minimize damages.  