In this session we will review key elements to take into account when migrating MySQL into the Cloud. We will share our experience of working with many different customers across the globe describing most effective procedures.
- IaaS vs DBaaS
- Migrating data
- Replication between On-Premises and Cloud
- Testing Cloud environments
- Load Balancers
- High Availability
We in Percona are constantly looking at how we can help our customers to have the right solution at the right time. We are constantly looking to identify the right tool for the job.
In our constant research we identified that migrating from Oracle, MS SQL or any other closed source data platform, is becoming more and more relevant for large organizations.
The maturity reached by open source solutions, the large adoption of those solutions in medium size companies or for new projects, in conjunction with the agility they have to adapt platforms to newer and more modern needs, had finally led large organizations/enterprises to understand that "It can be done".
Still the journey from closed source to open source is not always a walk in the park.
There are many factors that must be considered and analyzed, to successfully migrate.
There are simple situations, where a simple data migration with few schema adjustments is enough, and much more complex scenarios where to migrate, the whole logic must be reorganized.
Finally, there are situations where migrating is simply not possible or valuable.
Having a clear path that can help you to assess what is what, and how much effortis needed for each case, is gold. Literally, because it will allow you to focus on what makes sense, and the right effort and resources.
The scope of this presentation is to illustrate how we in Percona perform that assessment, and what is our methodology to assist our customer to successfully decide how and if to migrate.
Introductory-level session for database administrators interested in taking their first steps in migrating an existing Oracle database to PostgreSQL.
- What are the steps?
- What are the major challenges?
- Which tools should we use?
The session will focus on the basic steps, procedures and tools every DBA should use for migrating Oracle databases to PostgreSQL and will cover: source database migration assessment, schema conversion, data replication and performance tuning.
1. Overview of the five steps for database migrations: assessment and migration planning, schema conversion, data migration, application conversion.
3. Why planning and assessment is important for successful migration execution.
4. Key take-away insights from planning your migration that will impact implementation.
5. Using migVisor for the migration assessment.
6. Using Ora2PG for schema conversion.
7. Data replication: concepts, best practices and available tools.
Modern relational databases are all tied together by a well-defined standard for SQL, the latest version published in 2016. But not all SQL implementations follow the standard and even when they do, they often embellish on it and users tend to use the features they see available to them. As a result, migration between databases tends to be a challenging task. In this talk I will give some examples of database migrations I have participated in over the last twenty years and what issues we ran into with each. I will also talk in a more general sense about:
â€¢ Database only migration vs application refactoring - which is likely to have the better ROI?
â€¢ Analysis tools to help perform migration like Amazon's DMS, SQLines and DBconvert
â€¢ Database agnostic replication
â€¢ What it means to get support in the Open Source world and how to get it.
As more and more people are moving to PostgreSQL from Oracle, a pattern of mistakes is emerging. They can be caused by the tools being used or just by not understanding how PostgreSQL is different than Oracle. In this talk, we will discuss the top mistakes people generally make when moving to PostgreSQL from Oracle and what the correct course of action.
The Player Accounts team at Riot Games needed to consolidate the player account infrastructure and provide a single, global accounts system for the League of Legends player base. To do this, they migrated hundreds of millions of player accounts into a consolidated, globally replicated composite database cluster in AWS. This provided higher fault tolerance and lower latency access to account data. In this talk, we discuss this effort to migrate eight disparate database clusters into AWS as a single composite MySQL database cluster replicated in four different AWS regions, provisioned with terraform, and managed and operated by Ansible.
This talk will briefly overview the evolution of the player accounts services from legacy isolated datacenter deployments to a globally replicated database cluster fronted by our account services and outline some of the growing pains and experiences that got us to where we are today.