4.
Slide861All Things Microsoft run great on AWS Advanced Threat Analytics BizTalk Core Infrastructure Suite R Server Microsoft Office Exchange Server Project Server SharePoint Server Skype for Business Server SQL Server System Center System Center Server Visual Studio Visual Studio Team Foundation Server Windows Desktop Enterprise Operating System Windows Server MSDN Remote Desktop Services Microsoft Dynamics
5.
Microsoft Active Directory on AWSMicrosoft Active Directory on AWS Choices AWS Directory Service with AD Connector AWS Directory Service with Microsoft AD Microsoft AD on EC2
6.
AWS Managed Microsoft ADAWS Managed Microsoft AD AWS managed, actual Microsoft Active Directory Windows Domain Controllers (DC) ~3-click setup from directory service console or script through API 2 DCs each in separate Availability Zones (AZ) Scale-out with additional DCs Automatic patching, replication, and daily snapshots Compliance audited 750 hour free trial for new AWS Directory Service customers
8.
AD options – Connecting AD in cloud to on-premises ADAD options – Connecting AD in cloud to on-premises AD 1 Replication Your DCs only On-premises Windows Server DC AD VPC EC2 for Windows Server DC AD On-premises Windows Server DC AD VPC EC2 for Windows Server DC AD 2 1-way Trust 2-way Trust Your DCs or AWS Managed Microsoft AD On-premises Windows Server DC AD VPC EC2 for Windows Server DC AD 3 Sync Users Depends (third-party sync)
9.
Slide923SQL Server on AWS Performance? High Availability? Cost Optimization / Licensing?
11.
Slide1004High Availability in AWS Availability Zone-1 Availability Zone-2 Miles Apart Milliseconds Latency Workloads Workloads Clustering Load Balanced Application Storage Multi-Region Based Routing
12.
Slide957Deployment On-premises SQL HA/DR Architecture Data Center / Region HA Disaster Async Miles Apart Data Center / Region On Premises High Latency
14.
AlwaysOn Basic Availability GroupsAlwaysOn Basic Availability Groups •Available in Standard Edition •Limit of two replicas (primary and secondary). •No read access on secondary replica. •No backups on secondary replica. •No integrity checks on secondary replicas. •No support for replicas hosted on servers running a version of SQL Server prior to SQL Server 2016 Community Technology Preview 3 (CTP3). •Support for one availability database. •Basic availability groups cannot be upgraded to advanced availability groups. The group must be dropped and re-added to a group that contains servers running only SQL Server 2016 Enterprise Edition. •Basic availability groups are only supported for Standard Edition servers. •Basic availability groups can not be part of a distributed availability group. Availability Zone a VPC subnet Windows Server Failover Cluster M Availability Zone b VPC subnet S
15.
AlwaysOn Availability GroupsAlwaysOn Availability Groups •Available in Enterprise and Developer Editions •Up to 9 replicas (including primary). •Up to 3 synchronous replicas (including primary) •Each Replica can be standalone or AO FCI •Automatic failover from standalone instances to other synchronous replica •Option to run WSFC, external cluster (e.g. in Linux using PaceMaker), or without clustering (DB level availability) •Multiple databases per AG •Network Listener for transparent connections •Low-latency AWS multi-AZ architecture allows very high availability with minimum costs Availability Zone a VPC subnet Windows Server Failover Cluster M Availability Zone b VPC subnet S
16.
Distributed Availability GroupsDistributed Availability Groups Region 1 Region 2 Availability Zone a Availability Zone b WSFC 1 AG 1 Primar y Secondar y Availability Zone a Availability Zone b WSFC 2 AG 2 Forwarde r Secondar y Distributed AG Use-cases: •Multi-region DR •Migration •Read-replicas more than 8 (max in single AG)
17.
Slide955SQL Always On can be expensive.. Problem 1: In SQL Always On Setup: >1 Databases requires SQL Server Enterprise Edition SQL Standard Core= $3,717.00 SQL Enterprise Core = $14,256.00 (~4x more expensive) Possible Solution: FCI (Failover Cluster Instance) supports multiple databases with SQL Standard Edition Problem 2: requires Shared Storage (not available in public clouds)
18.
Always On Failover Cluster InstanceFCI Always On Failover Cluster Instance AWS Cloud Availability Zone a Availability Zone b DB files on shared storage Primary Secondary •HA at instance level •Standard Edition supports 2 nodes in AO FCI •Relies upon a shared storage available to all nodes •Available in both Windows and Linux •Only one instance of SQL Server runs at a time •No read access on secondary •Shared Storage options in Windows: •Storage Spaces Direct (S2D) •SIOS Datakeeper •Other custom solutions
19.
Slide968SQL Server Cost Optimisation with Dedicated Host §Single-tenant servers host instances for only your workloads (1 AWS Account) §You pay per host §You can continually reuse the same physical server through targeted placement, or let EC2 place your instances automatically §Visibility into physical cores and sockets (The use of Dedicated Hosts allows you use a per-core or per-socket SQL Server licensing model) Shared Tenancy - EC2 Instances Amazon EC2 Dedicated Hosts Customer 1 Customer 3 Customer 5 Customer 2 Customer 4 Customer 6 Customer X §Multi-tenant servers host instances for multiple customers’ workloads §AWS determines which host instances run on §You pay per instance R4 DH allows you to spin up the number of VMs designated on the table. 16 R4.Xlarge or 8 2XLarge etc https://aws.amazon.com/ec2/dedicated-hosts/pricing EC2 Instance
20.
Slide969Customer Requirement: Large Number of Database Servers: •Requirement (on Premises) •8 Database servers – each with •104 GB RAM •16 Cores •Instance in AWS •“r4.4xlarge” instance •122 GB RAM •16 vCPU SQL Server Cost Optimisation with Dedicated Host Problem: High SQL License cost due to 8 x 16 = 128 vCPUs. $ 887K (Windows STD + SQL ENT) Is there anyway to optimize?
21.
Slide970SQL Server Cost Optimisation with Dedicated Host •Need 8 x “r4.4xlarge” instance •122 GB RAM •16 vCPU Large Number of Database Servers: •Problem: SQL License cost for running 8 x 16vCPU) •$ 887K •Solution: SQL License cost for running 2 r4 dedicated host (36*2 cores, can run 8 r4.4xlarge instances) •$ 523K •41% Cost effective R4 DH R4 DH AZ1 AZ 2 R4.4xlarge R4.4xlarge R4.4xlarge R4.4xlarge R4.4xlarge R4.4xlarge R4.4xlarge R4.4xlarge SQL Always On Also BYOL for Windows Server
22.
Slide921SQL 2017 – SQL Linux •SQL Server 2017 Linux supported on Amazon EC2, RHEL license-included •Support Docker-based environments running on EC2 Windows and Linux •Cluster & cluster-less Availability Groups (WSFC, Pacemaker, None) SQL Server Linux AWS
23.
SQL Server on Amazon RDSSQL Server on Amazon RDS Managed Service Availability Zone 1 Private Subnet Availability Zone 2 Private Subnet Synchronous Commit Automatic Failover AWS Region Amazon RDS Primary Amazon RDS Secondary
24.
Amazon RDS is available for 6 different DB enginesAmazon RDS is available for 6 different DB engines Commercial Open source Amazon Aurora lets you deploy Microsoft SQL Server-based workloads with Amazon RDS MySQL Compatible PostgreSQL Compatible
25.
License Optimization with Optimize CPUsLicense Optimization with Optimize CPUs •Control active vCPUs and Hyper-Threading status when launching new EC2 instances •Reduce the number of SQL Server licenses *Sample licensing example only
26.
Migrating DatabasesImporting and Exporting SQL Server Databases Migrating Databases Importing and Exporting SQL Server Databases •Migrate databases to Amazon RDS. •Move databases between Amazon RDS SQL Server DB instances. •Import and export data. •Migrate schemas, stored procedures, triggers and other database code. •Backup and restore single databases •Testing, training, and demonstrations. Amazon S3 Amazon RDS
27.
Slide964AWS Database Migration Service Replication Instance SOURCE TARGET On-premises database Amazon RDS DB instance DB on EC2 instance On-premises database Amazon RDS DB instance DB on EC2 instance
28.
Migrating ServersAWS Server Migration ServicesMigrating Servers AWS Server Migration Services •Simplify the cloud migration process. •Orchestrate multi-server migrations •Test server migrations incrementally •Support the most widely used operating systems •VMware & Hyper-V support •Minimize downtime •Windows Server 2003 Support Server Migration
30.
AWS Systems ManagerAWS Systems Manager •Run Command •Maintenance Window •Inventory •State Manager •Parameter Store •Patch Manager Automation Deploy, Configure, and Administer Track and Update Shared Capabilities
31.
AWS Systems Manager Use CasesAWS Systems Manager Use Cases -Inventory Management (OS, Registry, Files, Services, Roles) -Patch Management (Linux, Windows Patch Mgmt) -Log Collection / Analytics (Collection of Windows Logs) -Automation (AMI Patching, Updating Auto Scaling Groups) -Security (Run Commands for remediation, storing secure credentials, replacing bastion host) -DevOps (built-in GitHub support to reference/run external files - Python, Ruby, YAML, PowerShell or Ansible ) -Custom Partner Solutions (DR, Agent Distribution, SAM) no cost
Thank you for your comment.