Preface
Galaxybase is the first ultra-large-scale distributed parallel native graph platform product independently developed by Chuanglin Technology in China. It has excellent data reading and writing query performance, powerful visual analysis capabilities, rich programmable interfaces and out-of-the-box graph algorithms. The engine is a one-stop management platform for the entire life cycle of graph data that integrates storage, calculation, and analysis. It meets customers' needs for efficient data storage and query in the era of big data.
At present, Galaxybase has been implemented in finance, energy, government, public security and other industries. In scenarios that require real-time query and analysis of complex related data, it can smoothly replace the original relational database or similar foreign products , helping enterprises to stimulate the value of data. . Traditional relational databases store data in the form of rows and columns. They are currently the database type with the highest market share, but they have limitations in specific business scenarios. Galaxybase Studio provides a way to use relational database modeling to help users complete the migration of relational database files to Galaxybase and realize automated modeling and data mapping. Currently, Galaxybase supports four relational databases: MySQL, SQL Server, Oracle, and PostgreSQL. This article will use the SQL Server database as an example to teach you how to complete data migration.
Data migration plan
Galaxybase Studio is a low-code visualization platform independently developed by Chuanglin Technology. It provides one-stop services such as drag-and-drop data modeling, mapping, loading, and querying. It currently has the capabilities of graphic mapping, table mapping, and relational database construction. Figure three methods, the specific process of using SQL Server database for modeling is as follows: database connection - successful connection - edit mapping content - load data - complete modeling - Figure project display.
Precautions
- Currently, only four relational databases: MySQL, SQL Server, Oracle, and PostgreSQL are supported;
- Before connecting to the database, you must add the corresponding database driver package in the cluster management-Driver extension, otherwise the database cannot be connected.
Step 1: Database connection
Click Create Diagram Project, select the method of using relational database modeling, and then enter the database connection page, as shown in the figure above. Fill in the parameters in sequence on the database connection page. After filling in, click Import URL to pop up the import window, as shown in the figure below. What needs to be noted in this step is that if the database connection is not successful, you are not allowed to enter the next step.
After entering the correct URL according to the example format, click the Confirm button to complete the import. Then check again whether all parameters are filled in correctly. After confirming, click the connect button to connect successfully, as shown in the figure below, the "Next" button lights up.
Step 2: Edit mapping content
After successfully completing the database connection, the system will jump to the edit mapping content page. As shown in the figure below, the Edit Mapping Content page supports modification of the names, comments, attributes, external unique identifiers, etc. of point types and edge types. Since the primary key is not set in this migrated data source table, the user needs to manually check the external unique identifier. If the primary key has been set in the original table, the system will automatically recognize it.
As shown in the figure below, after the check is completed, click to view the information. Check whether the data source information is consistent with the database connection. Here you can see that the server address, port number, database name, and user name are all consistent. After checking, click Confirm and Save to enter the data loading page.
Step 3: Load data
As shown in the figure below, after the mapping data is completed, the loading data page is entered. This step is relatively simple. Click Load and confirm to complete the data loading operation.
After loading data is completed, you can choose to go to the graph display immediately or return to the graph project. Here we return to the graph project and see if it has been migrated to Galaxybase Studio.
Migration result display
Returning to my graph project, you can see that the graph name is Modeled using a relational database, the number of points is 45, and the number of edges is 20. At this point, the data set has been successfully migrated from the SQL Server database to Galaxybase.
Conclusion
This article describes the operation process of migrating relational database SQL Server data to Galaxybase through the Galaxybase Studio visualization platform, successfully converting table structure data into graph structure form. In addition, the visualization platform provides minimal programming-free interactive functions, allowing business personnel to focus on the business itself, reducing code learning costs, and meeting the needs of multi-user collaborative exploration, large picture cutting and export, and multi-precision analysis.
In the follow-up, we will count the readers’ practical copy on the common issues raised by data migration during the replacement process with Galaxybase. For detailed questions, you can leave a message on the Galaxybase official account or ask questions on the official forum , and we will respond.