-
Notifications
You must be signed in to change notification settings - Fork 244
feat(rdb): migration index #5193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ldecarvalho-doc
wants to merge
3
commits into
main
Choose a base branch
from
MTA-6179
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
31 changes: 31 additions & 0 deletions
31
...ed-databases-for-postgresql-and-mysql/reference-content/migrating-databases.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
--- | ||
meta: | ||
title: Migrating to Scaleway Managed Databases for PostgreSQL and MySQL | ||
description: Learn how to migrate your PostgreSQL and MySQL databases to Scaleway Managed Databases for improved performance and scalability | ||
content: | ||
h1: Migrating to Scaleway Managed Databases for PostgreSQL and MySQL | ||
paragraph: Discover the benefits of migrating your PostgreSQL and MySQL databases to Scaleway Managed Databases and get step-by-step guidance on the migration process | ||
tags: databases postgresql mysql migration managed-databases | ||
dates: | ||
validation: 2025-06-26 | ||
categories: | ||
- managed-databases | ||
--- | ||
|
||
Scaleway Managed Databases allows you to run your Database Instances without setting up or managing infrastructure. Scaleway is responsible for implementing and maintaining features that improve the performance, scalability, security and high-availability of your Database Instances. | ||
|
||
If you have a self-managed database instance, or you use a different cloud provider, you can easily migrate your databases to Scaleway. | ||
|
||
Different factors, such as the size of your databases and your application use-case, can determine the best migration method. Below is a list of the different migration methods and their benefits, as well as a link to each of the tutorials that show you how to carry out your method of choice. | ||
|
||
| Database size | Downtime tolerance | Engine | Recommended migration method | Benefits | | ||
| --- | --- | --- | --- | --- | | ||
| < 100GB | Can afford downtime | PostgreSQL | [Dump/restore from local machine](/managed-databases-for-postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases/#using-pgadmin) | Easy, straightforward | | ||
| > 100GB | Can afford downtime | MySQL and PostgreSQL | [Dump/restore from a Scaleway Instance](/tutorials/migrate-databases-instance/) | Avoids local storage and bandwidth bottlenecks | | ||
| Any size | Cannot afford downtime | PostgreSQL | [Set up logical replication](/managed-databases-for-postgresql-and-mysql/api-cli/logical-replication-as-subscriber/) | Zero downtime, real-time data sync, flexible migration windows, easy rollback. Refer to the official PostgreSQL documentation for a list of [logical replication restrictions](https://www.postgresql.org/docs/16/logical-replication-restrictions.html) | | ||
|
||
|
||
|
||
|
||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Delete empty lines?