0

As my title mention I have a Master and a Slave database.

Master if for operations data and my slave mainly for reporting stuff.

The issue is that I need to create extra tables on reporting that can't be on the master, but the way my replication is set (the simplest one mentioned by the official doc) at the moment, this breaks the replication system.

How could I add tables on the Slave without Master caring about it ? Is it even possible ?

|improve this question
  • 2
    It is totally possible and should work without a problem on the slave in a simple/common/default configuration, so please explain what you mean by "this breaks the replication system." Do you mean theoretically? Or in your actual system? In what way does it break? – Michael - sqlbot Mar 27 '13 at 11:42
  • @Spredzy Are you not interested in this question? Can you answer Michael's question? – ypercubeᵀᴹ Jul 29 '13 at 21:50
  • Sorry I totally forgot about this thread back in the day, since I - at a later point - got the answer. When I initially though that creating table on slave was the issue, after debugging it further it revealed to be wrong, another action was acutally causing it. Creating the table on slave was fine. – Spredzy Jul 30 '13 at 12:24
1

I think I got a rough idea how you setup replication. I think you have taken mysqldump --all-databases ... something along those lines.

Now if you want extra tables inside one of those database that you exported by mysqldump and those that belong to the master replication will break as you mentioned aswell.

Now to create more tables you need to create a new database with some name and then create tables in there. This will not break the replication.

I do not know if this helps....

Masood

|improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.