Migrating from Relational Databases
Migration guidelines for relational database users. In this section, we use MySQL as an example relational database.
When migrating from MySQL to Couchbase Server, there are several things that you might want to think about, starting with the data model, data types, and feature set differences.
Data Model – Mapping from MySQL to Couchbase Server
Data modeling for RDBMS has been a well-defined discipline for many years. Professionals, including novice users, have been practicing techniques such as logical to physical mapping and normalization / de-normalization. However, the old-school RDBMS data modeling techniques still play a meaningful role for those who are new to the NoSQL technology.
|Fixed schema||Flexible schema|
|Data type||MySQL||Couchbase Server|
|Boolean||Yes (as tinyint)||Yes|
|Date time||Yes||Yes (as a string in JSON)|
Like MySQL, Couchbase Server offers a rich set of features and functionality far beyond those offered in simple key-value stores.
|Keys/Indexes||Primary keys on keys of (key, value) pair|
|Explain and metadata||Variation in command and results (JSON).|
You might have a spectrum of relational, operational, and analytical data sources in your environment. You might also need more sophistication applied to a data movement situation, such as more than just simple extract-load. In a case like that, you can use an extract-transform-load (ETL) tool such as Talend. With Talend, you can easily move data between Couchbase Server and any other data source.