One of the world’s largest multimedia content providers was looking for a way to increase the level of user satisfaction by improving the performance of their enormous database syste...
Typical challenges that we see
Determining which Database and infrastructure technology is a best fit in AWS
There are many approaches to database technology in AWS from infrastructure EC2 to managed RDS.
The key lies in understanding these points:
- What is your current database and infrastructure technology and what is the appropriate match in AWS
- What resources do you have to support your database technology in AWS and do those resources more closely favor a path to RDS or EC2?
- What is your HA/DR approach and will it be more easily mapped to RDS or EC2?
- What is your data egress and ingress and how will that affect your charges
DB Best can help you evaluate your current workload and direct you to the best technology approach within AWS.
Choosing which workloads to move to AWS
We take a data-centric approach to determine which workloads are most appropriate for the cloud. We start with data collection that gives us a profile of each workload environment such as CPU, RAM, etc. We then gather performance metrics over a period of time using our agentless DBMSys software. We also work with our customers to understand the business needs/restrictions of each workload to determine a list of potential candidates that can be moved to the cloud.
Building an AWS stack with multiple layers can be time consuming and error prone
The use of these tools along with our own automation tools perform deployment tasks such as:
- Setup your VPC
- Setup your subnets
- Setup your ELB
- Setup your EC2 instances
- Upload your databases
- Configure Auto-scaling groups
- Creation of S3 buckets
- Uploading data
- Restoring databases
- Configure your health checks
At DB Best, we have a set of entry-level offers to help you understand your modernization landscape and demonstrate the value of moving your Microsoft SQL Server workloads to Amazon RDS or EC2 instances.
We’ve designed our Data Management Optimization offer to monitor your on-premises SQL Server databases to determine the CPU utilization, IOPS requirements, memory needs, and network latency over a month. By looking at the server configurations and correlating the monitored data, we can recommend the optimal server machine types for deployment on EC2 and AWS RDS.
Sometimes you just need a little help. With the AWS Schema Conversion Tool (SCT), you can analyze your source SQL Server schema and code to determine compatibility with AWS RDS for SQL Server. Our team has unique experience using SCT, so we’ve created the AWS Schema Conversion Tool Jumpstart offer to provide a pool of hours to help you with your project.
Check out the offers below for more information on how we can help you with your migrating SQL Server to AWS RDS or EC2 efforts.
In this one-day course on Optimizing SQL Server on AWS RDS training, you will gain a better understanding on how SQL Server works on RDS. Let us help you write better queries and reduce operating costs!
Looking to upgrade your old MySQL, PostgreSQL, Oracle, and SQL Server databases or move them to AWS? Our Data Management Optimization (DMO) for AWS service provides you with recommendations and an ROI model for your digital transformation initiatives.
Trust the experts with the best knowledge of AWS DMS and the Schema Conversion Tool (SCT) to help move your on-premises databases to AWS RDS, Amazon Aurora, and Amazon Redshift.
One of the world’s largest multimedia content providers was looking for a way to increase the level of user satisfaction by improving the performance of their enormous database system. They wanted to leverage operational best practices to increase resiliency/uptime, performance, and scalability at the lowest possible cost. Their overall goal is to move all of their applications out of their datacenter and over to Amazon Web Services through a lift-and-shift process.
The first consideration we needed to help our customer through was determining which workloads should move to SQL Server running on EC2 instances versus SQL Server on RDS. AWS does provide a white paper Deploying Microsoft SQL Server on Amazon Web Services that features SQL Server 2014 written in 2016. Since then, Microsoft has shipped two new versions of SQL Server and AWS has made 12 major improvements to RDS for SQL Server including support for SQL Server 2017.
Considerations for RDS
Based on the criteria we gathered for high availability, disaster recovery, performance, scale, and SQL Server features used within the application, our default is to always consider RDS as the deployment target because of the great platform as a service features it provides. We then take a look at the following considerations:
- Are there any features that applications use that are not supported by AWS RDS for SQL Server? We use the reporting capabilities for the AWS Schema Conversion Tool (SCT) to identify incompatible features. AWS does a great job of updating to align with the ever-shrinking list of unsupported SQL Server features with RDS.
- Can we reduce the administrative burden with features like automatic backups, automatic patching, seamless replication, and super-easy point-in-time restore?
Considerations for SQL Server on EC2
- Use of unsupported features. SCT provides a report of the unsupported features and offers suggestions on how to work around the issues. If the workaround has little impact on the application code, then we will consider it based on the cost to deliver the change. On the other hand, if the workaround is significant, going with EC2 may make sense.
- Hardware resources are not sufficient to support performance and high availability. RDS instances are quickly aligning with the largest of instance types. As of July 2018, SQL Server 2016 & 2017 RDS on Enterprise Edition supports the db.r4.xlarge–16xlarge instance type with 64 vCPUs, with 195 ECUs, and 488 GiB. However, if a larger machine is required or there is a higher level of availability that requires a feature like Always On Cluster Failover Instances and/or Availability Groups, then EC2 is the answer.
Tools we use to migrate SQL Server to AWS RDS or EC2
Over the years, we’ve created our own set of products and tools to help upgrade SQL Server databases and deploy them to modern infrastructures. With these tools, our team can minimize the costs to ensure data integrity and minimize testing costs associated with migrating SQL Server to RDS or EC2 instances.
We are the only AWS partner who can say we've migrated more databases to AWS RDS, Amazon Aurora, and Amazon Redshift than any other partner in the world using AWS Database Migration Service (DMS) and Schema Conversion Tool (SCT).
See how we can help you optimize and future-proof your Microsoft data integration solution on-premises and on Azure.
We are a leading partner with Amazon who specializes in moving on-premises databases to the cloud. Learn how we can optimize your solutions using AWS data integration tools.
We have a great set of blog posts and datasheets to help you better understand our capabilities as the leader in database migration services showcasing our expertise in moving Microsoft SQL Server workloads to AWS Relational Database Service or EC2.
In order to modernize their existing applications, databases, and infrastructure, a major state-run university with nine campuses, approached DB Best with a desire to not only create t...
Our customer needed to reduce the licensing costs of their Oracle database. We came up with a comprehensive solution by migrating their database to SQL Server platform. We also remed...
A typical database migration project includes not only the schema conversion and data migration but also the application remediation. We are talking about one or many applications inte...
Reference data sheet
You may feel frustrated with high licensing costs and lackluster performances of your relational databases? Do you have some security worries about your data environment? Still won...