{"id":6650,"date":"2024-07-16T08:45:00","date_gmt":"2024-07-16T07:45:00","guid":{"rendered":"https:\/\/dasini.net\/blog\/?p=6650"},"modified":"2024-08-06T10:29:53","modified_gmt":"2024-08-06T09:29:53","slug":"get-your-heatwave-mysql-data-on-premises-with-replication","status":"publish","type":"post","link":"https:\/\/dasini.net\/blog\/2024\/07\/16\/get-your-heatwave-mysql-data-on-premises-with-replication\/","title":{"rendered":"Get Your HeatWave MySQL Data On-Premises with Replication"},"content":{"rendered":"\n

MySQL Replication exist for centuries… OK, I’m exaggerating a little bit \ud83d\ude42 but this feature is as much appreciated as it is useful, because is helping DBAs to easily build scalable and redundant architectures:<\/p>\n\n\n\n

\n

MySQL 3.23.15 and up features support for one-way, asynchronous replication, in which one
server acts as the master, while one or more other servers act as slaves<\/p>\nMySQL 3.23\/4.0\/4.1 Reference Manual<\/cite><\/blockquote>\n\n\n\n

At least from MySQL 3.23… I told you it’s been there for a long time: MySQL first Public Releases<\/a><\/p>\n\n\n\n

But what does replication do?
Quoting the documentation again (the most recent this time<\/em>)<\/p>\n\n\n\n

\n

Replication enables data from one MySQL database server (the source<\/strong>) to be copied to one or more MySQL database servers (the replicas<\/strong>).
Replication is asynchronous by default; replicas do not need to be connected permanently to receive updates from a source.<\/p>\nMySQL 8.4 Reference Manual<\/cite><\/blockquote>\n\n\n\n

<\/div>\n\n\n\n

In this article we will see how to replicate data from HeatWave MySQL<\/a> to a on-premise standalone MySQL Instance.<\/p>\n\n\n

\n
\"Get<\/figure><\/div>\n\n\n