Add migration guides #1183
Open
Add migration guides #1183
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Josipmrden
added
the
priority: medium (missing info)
…into migration-guides
matea16
requested changes
Apr 29, 2025
| @@ -6,10 +6,14 @@ description: Easily transition from RDBMS to Memgraph using MAGE modules. Our de | |||
| # Migrate from RDBMS to Memgraph using MAGE modules | |||
|
|
|||
| This tutorial will help you import your data from a PostgreSQL database into Memgraph | |||
| directly using MAGE query modules. | |||
| directly using the [Memgraph MAGE `migrate` module](/advanced-algorithms/available-algorithms/migrate). | |||
There was a problem hiding this comment.
Suggested change
| directly using the [Memgraph MAGE `migrate` module](/advanced-algorithms/available-algorithms/migrate). | |
| directly using the Memgraph MAGE [`migrate`](/advanced-algorithms/available-algorithms/migrate) module. |
| This way of migrating data into Memgraph requires exporting the data from the source relational | ||
| database system into CSV files, and then importing them into Memgraph. For direct data import | ||
| from a relational database system to Memgraph, please check out | ||
| our (guide for using migration modules inside Memgraph MAGE)[/data-migration/migrate-from-rdbms-directly]. |
There was a problem hiding this comment.
Suggested change
| our (guide for using migration modules inside Memgraph MAGE)[/data-migration/migrate-from-rdbms-directly]. | |
| our [guide for using migration modules inside Memgraph MAGE](/data-migration/migrate-from-rdbms-directly). |
| import { Callout } from 'nextra/components' | ||
| import {CommunityLinks} from '/components/social-card/CommunityLinks' | ||
|
|
||
| # Migrating data lake data from Apache Iceberg to Memgraph using Dremio |
There was a problem hiding this comment.
Suggested change
| # Migrating data lake data from Apache Iceberg to Memgraph using Dremio | |
| # Migrate Data Lake data from Apache Iceberg to Memgraph |
| # Migrating data lake data from Apache Iceberg to Memgraph using Dremio | ||
|
|
||
| ## Overview | ||
| Migrating data from an **Apache Iceberg** table stored in a data lake to **Memgraph** can be efficiently done using **Dremio** as a query |
There was a problem hiding this comment.
Suggested change
| Migrating data from an **Apache Iceberg** table stored in a data lake to **Memgraph** can be efficiently done using **Dremio** as a query | |
| Migrating data from an [Apache Iceberg](https://iceberg.apache.org/) table stored in a data lake to **Memgraph** can be efficiently done using [Dremio](https://www.dremio.com/) as a query |
|
|
||
| ## Overview | ||
| Migrating data from an **Apache Iceberg** table stored in a data lake to **Memgraph** can be efficiently done using **Dremio** as a query | ||
| engine and Memgraph’s **migrate module**. This setup eliminates the need for manual data exports and enables real-time data streaming into Memgraph. |
There was a problem hiding this comment.
Suggested change
| engine and Memgraph’s **migrate module**. This setup eliminates the need for manual data exports and enables real-time data streaming into Memgraph. | |
| engine and Memgraph’s [migrate](/advanced-algorithms/available-algorithms/migrate) module. This setup eliminates the need for manual data exports and enables real-time data streaming into Memgraph. |
| memgraph.execute("CREATE INDEX ON :Person") | ||
| memgraph.execute("CREATE INDEX ON :Person(id)") | ||
| ``` | ||
| #### Why `IN_MEMORY_ANALYTICAL` is important for multithreading |
There was a problem hiding this comment.
Suggested change
| #### Why `IN_MEMORY_ANALYTICAL` is important for multithreading | |
| {<h4 className="custom-header">Why `IN_MEMORY_ANALYTICAL` is important for multithreading</h4>} |
| Setting **STORAGE MODE IN_MEMORY_ANALYTICAL** allows Memgraph to operate entirely in memory, maximizing data | ||
| processing speed and enabling efficient multi-threaded execution. This mode significantly improves performance for analytical queries and bulk inserts. | ||
|
|
||
| #### How `DROP GRAPH` instantly clears the dataset |
There was a problem hiding this comment.
Suggested change
| #### How `DROP GRAPH` instantly clears the dataset | |
| {<h4 className="custom-header"> How `DROP GRAPH` instantly clears the dataset </h4>} |
| Executing **DROP GRAPH** removes all existing data in Memgraph instantaneously. This ensures that each ingestion | ||
| process starts with a clean slate, avoiding conflicts and ensuring consistent performance. | ||
|
|
||
| #### Why indexing improves relationship ingestion |
There was a problem hiding this comment.
Suggested change
| #### Why indexing improves relationship ingestion | |
| {<h4 className="custom-header"> Why does indexing improve relationship ingestion </h4>} |
|
|
||
| print(f"✅ Relationships successfully ingested into Memgraph after {(rel_ingest_end_time - rel_ingest_start_time):.2f}s!") | ||
| ``` | ||
| #### Optimizing relationship ingestion |
There was a problem hiding this comment.
Suggested change
| #### Optimizing relationship ingestion | |
| {<h4 className="custom-header"> Optimize relationship ingestion </h4>} |
Comment on lines
+22
to
+23
| **In order to learn all the pre-requisites for importing data into Memgraph, check | ||
| [import best practices](/data-migration/best-practices).** |
There was a problem hiding this comment.
Suggested change
| **In order to learn all the pre-requisites for importing data into Memgraph, check | |
| [import best practices](/data-migration/best-practices).** | |
| In order to learn all the prerequisites for importing data into Memgraph, check | |
| [import best practices](/data-migration/best-practices). |
|
One more note, update the main Data migration page with the newly added pages |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release note
Added new migration guides, and an overview page of supported source systems
Related product PRs
PRs from product repo this doc page is related to:
(paste the links to the PRs)
Checklist:
bugfixorfeaturelabel, based on the product PR type you're documenting