Tag Info

Hot answers tagged

3

There's three separate parts to this: Q: Do I use SQL Server's built-in log shipping or roll my own? A: I'd roll your own. What you're doing is beyond what the built-in tools are normally used for. Q: If I roll my own, where do I start? A: I'd use normal SQL Server full and transaction log backups on the primary. On the secondary, start with MSSQLTips' ...


2

well, you cannot switch back easily. what you can do is to use the old backup method: SELECT pg_start_backup('whatever'); rsync the data dir SELECT pg_stop_backup(); this is the best way as not all the data has to be transported over the network. i definitely recommend this replacement for pg_basebackup because it is the only RELIABLE way to get things ...


2

In general, actively writing to multiple masters in MySQL is a bad idea. MySQL Replication is asynchronous, which means there's no guarantee the changes make it to the slave before the changes are committed on the master. The implication is that something™ (node dies, slave lag, etc) can/will go wrong with one of the masters at any time. If your ...


1

you may need to grant super privileges to the user. Replication client is responsible only to replicate binary logs to slave


1

If you are not writing directly on your slave, no binary logs will get generated by default. To capture the binary log events from the master into the slave's binary log, you need two things: enable log-bin enable log_slave_updates


1

Here are two possible setups you could try TOPOLOGY #1 Data Center #1 with two(2) DB Servers (DB1, DB2) Data Center #2 with two(2) DB Servers (DB3, DB4) Setup DRBD with Each Data Center Setup MySQL Replication Between the DRBD Primaries Setup DBVIP (Linux Heartbeat/ Pacemaker / ucarp) What this setup provides Synchronous Disk-Level Replication Within ...


1

This is a permissions issue and you can find more details in the verbose agent log. Verify that your replication agent process accounts have the necessary permissions listed in the section Permissions That Are Required by Agents in Replication Agent Security Model. Note that Microsoft recommends that you use a Windows accounts for replication agent process ...


1

Some might say depends how big the databases are; I think regardless of the size, accessing the databases directly instead of having a "local" mySQL database to query would be best, for the following reasons: No need for disk/memory/maintenance of the mySQL database If the updates to the various databases happen every few seconds, and the users may only ...


1

It sounds like what you are looking for is an Always On Availability Group in Synchronous Commit mode with automatic failover. The transactions sync from the primary to the secondary and in the event of a system failure, will pass ownership of the database to the secondary. Your application would need to be aware of both the primary and secondary and which ...


1

Is it acceptable to have downtime on this database? This was probably either restored from a replicated database or it was possibly a subscriber that was improperly removed, though that is unlikely. You could try doing a backup from express and restoring to a standard or higher edition then setting up replication again and removing it. Then you can backup ...


1

As Antonis said, the number of connections has little relation to the number of databases. In general, the number of connections aren't something to worry about. The MongoDB drivers keep the connections alive to reuse them and to prevent the overhead of setting up new connections. However, each connection is provided with about 1MB of stack server side. ...


1

The filtered replication is not something that is currently implemented in MongoDB out of the box. That said, the replication in MongoDB is based on a special collection named "oplog", that you can listen to and do the filter yourself, and in this case implement the filter you want to push data into another cluster. (This will be viewed as 2 different ...


1

MongoDB at least to current version 2.6+ for sure does not support that as build-in functionality. I guess because a replica set using selective replication won't be consistent. There is a feature called filtered replication in Couch but never tried it: http://wiki.apache.org/couchdb/Replication#Filtered_Replication


1

I don't have experience of your exact situation, but could you use: auto_increment_increment=3 auto_increment_offset=1 [then 2 and then 3] on your different masters, so that each one generates a different set of id's. e.g. server 1: 1, 4, 7 server 2: 2, 5, 8 server 3: 3, 6, 9



Only top voted, non community-wiki answers of a minimum length are eligible