I asked questions about a warm standby and multicast replication. We ended up using bi-directional replication and a warm standby db. Having 3 or more live OLTP DB's where each was read-write was going to be difficult to manage for contention if the same table was being updated. We stuck with an easier solution to have only two OLTP's, and then used additional DB's as read-only DW's.
It's a great tool when building the software, the ability to add SQL and No-SQL databases. Very convenient to write the queries and generate the filtered data we require. Gives the ability to export, import databases of various formats and generate reports from them. It might not be suitable if you want the data to be seen in a visualized manner
It crashes CONSTANTLY. If you have more than one connection tab open and close one of them, it crashes. If you just have it open in the background, it randomly crashes. If you're using it, it randomly crashes. When you try to send a crash report, the CRASH REPORTER CRASHES.
Can be a bit slow.
No way that I'm aware of to query multiple databases in the same query.
SAP support has been outstanding. They have quick response times and always meet their SLAs. Any time we have an issue that needs to be researched they are able to get back to us quickly with resolution.
It's open-source and very convenient to work with. I can easily import any database I want using a data dump and runt the queries on them to derive the data insights on the data. I might want to use Excel to visualize that, that might be one of the disadvantages.
MySQL Workbench is a wonderful tool, but the routine editing of existing data is note nearly as straightforward as it is in Sequel Pro. The ability to sort a data view with a single click makes Sequel Pro my definite choice. phpMyAdmin is pretty ubiquitous, but the routine editing of existing data is much more cumbersome than it is in Sequel Pro.