Hot answers tagged replication
4
This will work fine. The only caveat is that if you, in the future, create a view on the master with the same view name, in the same schema, replication will stop due to the conflict.
Another potentially useful thing you can do -- quite safely -- on a slave server is adding indexes to base tables to help your reporting queries, even if the same index ...
3
It's highly unlikely you'll find a better merge replication solution than what's built-in.
Merge replication in particular is hard to implement.
I would suggest that if you're having issues with the current setup breaking, take it up with Microsoft. They should be very motivated to help you find the root cause of the problem so their customers are happy, ...
3
Replication from one box to area servers, then having those area servers replicate to the store servers within that area is easy. Setting up the replication to feed from two different area servers to each store server isn't really going to be doable. You could probably hack it to work, but it wouldn't be all that easy.
You would be better off setting up ...
2
It depends a great deal on your workload - the write volumes and write patterns on the master.
The standby is essentially doing continuous crash recovery. It reads write-ahead logs containing the changes the master made to the tables and applies that to its own tables. It does this using a single worker, so it doesn't benefit significantly from I/O ...
2
This is the sort of thing that Microsoft Consulting Services can help you with. They know replication really well, and setting up large merge replication farms needs to be done just right or the whole thing will come crashing down.
If there are specific errors that need troubleshooting you can post those here so that they can be figured out, but if it's ...
2
Depends how much data you need on the second database. Solutions are not to save query results on a second DB but duplicate data for querying on another DB. Basically the following techonologies:
Oracle Streams: it is a replication from one database to another one. Can be done by table or by schema.
Oracle Active Dataguard: it is basically a standby DB ...
1
Terminology
What you're describing is a common set up that may be variously described as master-master replication, dual-master, active-active, bidirectional, or a few other terms.
Good reasons not to do it
The team who wrote High Performance MySQL offer this pithy summary of master-master replication - specifically, "active-active" replication:
In ...
1
There is no such feature at this time and the transaction logs lack some of the key information you would need to implement such a feature.
Work is ongoing for PostgreSQL 9.4 to implement logical and bi-directional replication between PostgreSQL instances. Part of this work involves enhancements to the xlogs to add some key information required for logical ...
1
it seems the binlog doesn't include the new inserts
I'm not sure whether you're saying the binlog actually doesn't include them, and you have confirmed this with mysqlbinlog, or that it "seems" like it doesn't, because they don't replicate.
PXC needs log_slave_updates turned on at the node serving as master to the asynchronous slave, otherwise, not ...
1
Binary Log Format : I was thinking that since Percona XtraDB Cluster (PXC) required using binlog_format as ROW, all the read-only Slaves should also have that setting.
binlog_do_db : It will record every option for a given database only. Notwithstanding, this is an option that is sometimes misunderstood. Please read this blog entry from mysqlperformanceblog ...
1
I have 8 individual SQL Server 2008 R2 machines, each hosting 1 database. Each database has an identical table structure and schema, and entirely unique data.
I would like to establish a reporting server (may be 2008 or 2012), that consolidates the rows from selected tables across the 8 source servers into a single instance of those tables on the ...
1
If you have access to a db version control system (ala Red Gate), you can have it create a deployment script fairly easily.
If not, just create a file and script any ddl changes you make and store them in a file, then when you are ready (and have backed up prod) you can run the script against prod to make your changes.
Be aware that certain changes can ...
1
The general recommendation is to have all members of a cluster or replica set running the same version, inclusing arbiters. Hence, generally you should upgrade arbiters when you upgrade everything else. In fact I would say to upgrade them first since if you have things configured correctly there will be no interruption in terms of operations from an ...
Only top voted, non community-wiki answers of a minimum length are eligible
