Hot answers tagged

7

A solution that will work with SQL Express would be ideal, SQL Standard is fine, but I dont want to have to upgrade to SQL Enterprise. If you want something straight out of the box, that's going to be difficult to find. However, 2016 does bring Standard Edition Availability Groups. Standard Edition before 2016 does have Mirroring. Additionally if you'...


3

A fast refresh would copy incremental changes over the network but requires that a materialized view log be created on the master site on the source table. That adds some overhead to the inserts happening on the master table but would generally make the refresh more efficient. A complete refresh would copy every row over the network every time the ...


2

In a Galera cluster, any node can play the part of a Master node. Such a node can execute DML (INSERTs, UPDATEs, and DELETEs). If DML statements are spread across multiple Master nodes and are targeting the same tables, you must expect log conflicts. Why ? Galera wsrep libraries were designed to commit DML changes if all nodes in a cluster are ready to do ...


2

This information may not be of interest to the DBA. If the application is handling conflicts correctly, there is no need to log them. It would be expected behaviour. You would only enable this level of logging if you were debugging a specific issue. Otherwise it would generate a lot of spam in the logs.


2

Set up slave You can set it up from the nightly backups. That's actually a common practice to provision slaves from backups to also have them tested. You can go back as far as you have binlogs stored on the master (expire_log_days variable). The impact of having a slave starting from older backup is that it has to fetch the logs from the master but that ...


2

An alter procedure would not normally be replicated and so would not cause any problems. More than likely you're doing DDL operations and changing the tables and this is breaking the replication. Michael Keleher has suggested your replication may not be set up to replicate schema changes: Open the properties of the publication, go to the Subscription ...


1

Do not see the problem. When somebody enters the email address a second time then this happens. Nothing to do with replication. This is what the unique key is used for. If this error would break the replication then I do not understand how replication could ever work. Every user could easily break the replication by, in this case, entering an email address ...


1

I believe whenever transactional replication is initialized, the Publisher snapshots the articles in the publication and pushes it across to the subscriber. The remote Distributor and pull subscriber are used for the transactions after replication has been setup and initialized.


1

In the answer you linked to, Craig says: It's possibly practical to do it with minor changes to PostgreSQL( if all the servers are read-only, but I haven't investigated it as it's a pretty uninteresting use-case. (emphasis mine). The problem is, there is no way to start a PostgreSQL server and tell it "you are only allowed to look at this data ...


1

This should not a problem, provided you do not execute any DDL related to the Storage Engine on the Master. I have written about this many times Jun 01, 2011 : What can we do in MySQL 5.0 Replication to address bandwidth concerns? Nov 16, 2011 : Log MySQL DB changing queries and users Mar 13, 2012 : http://dba.stackexchange.com/questions/14943/setting-up-...


1

Solution for restoring a published database We faced a similar problem: A published database is stored on Server1. Every day this database will be backed up and restored on Server2. We frequently got error Messages "LOG full due to REPLICATION". log_reuse_wait_desc was set to REPLICATION. Replication could not be removed, because this database was not ...


1

The exact reason of why this happens, is because SESSION variables are replicated explicitly in the binary log. Here is an example of an entry header in the binary log: # at 368008153 #160624 9:15:24 server id xxxxx end_log_pos 368008235 Query thread_id=1097746 exec_time=0 error_code=0 SET TIMESTAMP=1466774124/*!*/; SET @@session.pseudo_thread_id=...



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