Tag Info

New answers tagged

0

where will that data be saved by default ? Agent history clean up: distribution calls EXEC [distribution_db_name].dbo.sp_MShistory_cleanup @history_retention = 48 This PROC deletes from MSsnapshot_history , MSlogreader_history, MSdistribution_history, MSqreader_history and MSmerge_history and bunch of other tables. This is the entire code for a ...


0

While replicating from a MySQL 5.0 Master to MySQL 5.6 Slave is allowed, it is not good to keep that scenario indefinitely. Why ? The way MySQL 5.6 reconnects to an older Master may be more difficult with older Masters. To illustrate problems of this nature, consider how MySQL Replication can break between versions because of Binary Logs changing between ...


0

If you need to do this with minimal downtime and have 100% confidence that you have consistent slave here are step by step direction how to rebuild the slave using Linux LVM. Preparation Set innodb max dirty pages percent to zero on the master. This will force MySQL to write all the pages to the disk which will significantly speed up the restart. set ...


2

The data should be "the same" as on my machine, that I can dismiss my server and point to new machine in the end. Based on your comments, your best option would be Database Mirroring or Log shipping. You have to evaluate your RPO and RTO. Since you are using VPN to your actual machine - meaning it is point-to-point connection : If you go with ...


2

It sounds like you're trying to setup a disaster recovery environment, so that if your local machine blows-up you can switch over to the Azure machine. There are a number of options, each with their own pros and cons. These are well documented elsewhere (see this link for an overview from Brent Ozar: ...


0

On your Slave issue the STOP SLAVE, START SLAVE commands to stop / start replication on Demand. If you want to run it to a schedule write a batch file / cron to STOP SLAVE and START SLAVE at the required times. I'm assuming you have a good reason for doing this?


0

You have 3 types of replication: Snapshot Transactional Merge Reference Link - Selecting the Appropriate Type of Replication Per Microsoft, these are easily broken down into two broad categories: Server to Server Server to Client In the scenario of Point of Sale (POS). You are recommended to use Merge Replication due to it's Server to Client ...


0

It is possible (but not simple). I just made the implementation of ORACLE to TimesTen real time replication. The solution is based on ORACLE LogMiner utility. Using this tool you can generate the ORACLE transactions in a real time and then ship them to the program (TimesTen side) which will read and apply those transactions to the TimesTen database. The ...


0

I ended up using F5 BIG-IP LTM Virtual Edition, because I didn't find any other free solutions, that fits my business requirements.


2

#5: transactional replication. Why is this an option? Because the documentation explains exactly why it is possible there - once initialized, index changes are not replicated in either direction. Indexes can be added at the Publisher or Subscribers with no special considerations for replication (be aware that indexes can affect performance). CREATE ...


1

I ended up using a post-initialization script to grant this permission at the subscriber and it worked great.


0

I have since come to learn, from this SO thread, that it is possible to do what I asked in my question. And it prevents rows inserted/updated/deleted on the source from being replicated to the destination.


2

I believe your DBA is referring to Publishing Stored Procedure Execution in Transactional Replication. With Transactional Replication you have the option to published the definition of the stored procedure or the execution of the stored procedure. Publishing stored procedure execution can provide significantly better performance for large batch operations ...


1

1) If we can set up the transactional replication between server A of version 2014 and server B of version 2012. Tried to Google out but could not find the exact documents because may be am looking somewhere wrong. Please suggest if it can be set up? For your replication to work, the PUBLISHER and DISTRIBUTOR should be on same version. The subscriber ...


2

For querying secondary run the following command first. After running this, you can do all regular stuff on secondary. rs.slaveOk() To see the replication status, run the following command on primary. This will show you if the secondaries are up to date or lagging. db.printSlaveReplicationInfo() Hope this helps.


0

Here is one for the ages I wrote an answer to a post on Jan 02, 2015 entitled mysql replication master 5.5 slave 5.1 error on create database. In that post, I learned from my boss about this strange situation when I was replicating from a MySQL 5.5 Master to a MySQL 5.6 Slave. In short, I learned from some additional research that binary log events can ...


0

Two possible reasons seem to stick out, ensure your server_id is different on both the master and the slave. This is to be defined at startup in the cnf file. Another option is you specified a very tiny max_binlog_size or max_relay_log_size, ensure the values are what you want and not off by an order of magnitude (eg. 512k instead of 512M)


0

I looked in to the declaration of sp_changemergepublication and found out the way it invalidates the snapshot is a simple query to update the table sysmergepublications if (@property like 'ftp%' OR @property in ('sync_mode', 'snapshot_in_defaultfolder', 'alt_snapshot_folder', 'pre_snapshot_script', ...


0

Replication from MySQL 5.x to 5.6 has a bear trap just waiting for you. In Michael's comment, he stated the politically accept premise : "MySQL supports replication from one major version to the next higher major version.". He also said "this setup isn't guaranteed to work in either direction." I have a very interesting caveat on going from 5.x to 5.6: ...


2

Cringe, gag, etc. 5.1 and 5.6 differ by 2 major versions. Replication is 'guaranteed' to work one direction, not the other. Don't turn on GTIDs in 5.6; 5.1 will not like it. Don't use any features new to 5.5 or 5.6. Simply, don't do it. Get the 5.1 upgraded ASAP.


0

The Slave should be irrelevant, unless you are using (misusing) some form of parallel execution on the Slave. Try other transaction_isolation_modes. GET_LOCK()/RELEASE_LOCK() may provide a sufficient "lock"; but all writers to that table(s) would need to use it. Do not turn on auto-reconnect in your connection. An network glitch will mess with both the ...


0

You have described a common way to make DDL changes. Yes, it should work. But... please describe the datatype change further. If you are ALTERing a COLUMN that is current INT SIGNED to be a SMALLINT SIGNED, and if none of the values are bigger than 32767, there should be no problem. If you are changing from SIGNED to UNSIGNED, and none of the numbers ...


1

slave-skip-errors can hide even serious errors; don't do it. Turn on the "general log" briefly. This should capture a little more info about where the duplicate DELETE is coming from. One of two things will happen: There will be two DELETEs in the general log, too. This will point at the application for issuing the delete twice. There will be one in ...


1

Yeah, what the heck is tmp_user? This smells like an attack. And I suspect it was successful. He probably already got in -- all he had to do was to try different flavors of the INSERT based on different versions. The one successful insert would suffice. Then he RENAMEs tables, does damage, rename tables back, DROPs evidence of his naughtiness, and ...



Top 50 recent answers are included