Skip to content

Commit 4710c73

Browse files
Update Migrating your existing Production DB.md
Removed/replaced outdated links to MariaDB docs, removed redundant and outdated sections, general cleanup and formatting
1 parent 9182f98 commit 4710c73

File tree

1 file changed

+12
-44
lines changed

1 file changed

+12
-44
lines changed

docs/Data loading, Migration/Migrating your existing Production DB.md

Lines changed: 12 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,23 @@
11
# Migrating your existing Production DB
22

3-
Databases can be migrated to MariaDB SkySQL from many different database platforms, including Oracle, MySQL, PostgreSQL, Microsoft SQL Server, IBM DB2, and more
3+
Databases can be migrated to SkySQL from many different database platforms, including Oracle, MySQL, PostgreSQL, Microsoft SQL Server, IBM DB2, and more.
44

55
# Lift-and-shift from a compatible version of MySQL/MariaDB to SkySQL
66

77
To perform a lift-and-shift migration to SkySQL, use the following process:
88

9-
1. Identify requirements for your MariaDB SkySQL implementation including:
10-
- [Topology](https://mariadb.com/docs/skysql-previous-release/features-and-concepts/services/)
11-
- [Instance size](https://mariadb.com/docs/skysql-previous-release/features-and-concepts/selections/instance-sizes/)
9+
1. Identify requirements for your SkySQL implementation, including:
10+
- Topology
11+
- Instance size
1212
- Storage requirements
1313
- Desired server version
14-
2. [Deploy the desired configuration](https://mariadb.com/docs/skysql-previous-release/service-management/launch/) on MariaDB SkySQL
14+
2. Deploy the desired configuration on SkySQL
1515

16-
<aside>
17-
💡 When migrating from a production DB a common practice is to setup live replication to the SkySQL database. Here is the sequence of steps you should follow for a live cutover:
18-
19-
</aside>
20-
21-
1. On the source database (MySQL or MariaDB) obtain the Binlog file name and its current position. Essentially, we want to track all DB changes from a certain point in time. See [‘Replicating data’](Migrating%20your%20existing%20Production%20DB%208ba80cbdb9b14f81a1df5b096d549522/Replicating%20data%20from%20external%20DB%20cdf15e1cd8d24880858d6cd2f50d8fd2.md) page for the command.
22-
2. Next, take a [dump of your source database using mysqldump or mariadb-dump](Import%20data%20from%20external%20DB%209d0a68120e404f36b9f09a5ad71796b7.md)
23-
3. Import into your target SkySQL DB using this logical “dump” (SQL)
24-
4. Finally, turn ON the replication using the SkySQL ‘start_replication’ procedure as noted below.
25-
26-
# Assisted Migration to SkySQL MariaDB
27-
28-
SkySQL customers can receive assistance from SkySQL Inc when migrating a database to SkySQL:
29-
30-
- SkySQL Inc's [migration process](https://mariadb.com/docs/skysql-previous-release/migration/assisted/#Migration_Process) divides a migration into multiple well-defined stages with distinct validation criteria at each stage
31-
- SkyDBAs and SkySQL support can assist with many migration steps
32-
33-
For assistance with a migration:
34-
35-
- Existing customers can submit a [support case](https://mariadb.com/docs/skysql-previous-release/service-management/support/) to request assistance with a migration
36-
- New customers can [contact us](https://mariadb.com/docs/skysql-previous-release/contact/) to begin the migration planning process
16+
---
3717

38-
## Migration Process
18+
# Assisted Migration to SkySQL
3919

40-
We use a multi-step process to assist customers with migrations:
20+
Our [SkyDBA team](https://skysqlinc.github.io/skysql-docs/FractionalDBA/) can help design a migration plan to suit your needs. We use a multi-step process to assist customers with migrations:
4121

4222
1. **Assessment** of application requirements, inventory, and identified challenges
4323
2. **Schema Migration** including tables, constraints, indexes, and views
@@ -46,27 +26,15 @@ We use a multi-step process to assist customers with migrations:
4626
5. **Quality Assurance** to assess data validity, data integrity, performance, accuracy of query results, stored code, and running code such as client applications, APIs, and batch jobs
4727
6. **Cutover** including final database preparation, fallback planning, switchover, and decommissioning of old databases
4828

49-
For additional information, see "[Whitepaper: Migrate to MariaDB from Oracle](https://go.mariadb.com/GLBL-WC2020OracleMigration_LP-Registration.html)".
50-
51-
---
52-
53-
# Migrate to MariaDB SkySQL using AWS DMS
54-
55-
This blog article details how to [Migrate RDS MySQL to SkySQL MariaDB Using AWS Data Migration Service](https://go.mariadb.com/21Q3-WC-GLBL-DBaaS-Amazon-RDS-to-SkySQL-Migration-DB1109_LP-Registration.html)
29+
- Existing customers can submit a [support case](https://app.skysql.com/dashboard) to request assistance with a migration
30+
- New customers can [contact us](mailto:support@skysql.com) to begin the migration planning process
5631

5732
---
5833

5934
# Replicating data from an External DB
60-
Click [here](Replicating%20data%20from%20external%20DB%20cdf15e1cd8d24880858d6cd2f50d8fd2.md) for a detailed walk through of the steps involved.
61-
62-
63-
For assistance with a migration:
64-
65-
- Existing customers can submit a [support case](https://mariadb.com/docs/skysql-previous-release/service-management/support/) to request assistance with a migration
66-
- New customers can [contact us](https://mariadb.com/docs/skysql-previous-release/contact/) to begin the migration planning process
67-
68-
## Best Practices
35+
Click [here](Replicating%20data%20from%20external%20DB%20cdf15e1cd8d24880858d6cd2f50d8fd2.md) for a detailed walk through of the steps involved.
6936

37+
---
7038

7139
### Live Replication for Minimal Downtime
7240

0 commit comments

Comments
 (0)