replication

In Sql Server2008 R2 and Windows Server 2008R2, when I start Replication I have this error: TCP Provider: The semaphore timeout period has expired Please help me to solve it. in order to fix the error: System.IO.IOException: The semaphore timeout period has expired. ​Solution​ I have done below NIC changes to resolve this error. Open the Network and Sharing Center. Right click on Ethernet Adapter>>Properties Select Client for Microsoft Networks Click on Configure Tab Click on Advanced Tab And then - Disable the below settings IPv4 Checksum offload Large Send Offload V1(Ipv4) Large Send Offload

Is there a way to replicate a sql server database but not push out deletes to the subscribers? Do this....Drop the article. Create a new storedprocedure in the corresponding database that mimicks the system store procedure (sp_del...) and contains the same parameter but does nothing. Add the article again...and set the delete store procedure under the article's properties to the new delete stored procedure that you created.... Or you can select Do not replicate Delete Statements....I think that works but i haven't tried it. You don't mention which version of SQL Server you're running, but Andy

We have a master-slave setup running Solr 6.5.0. There is a backend process running 24/7 which pushes its data towards the master server. No commit is done on master. The web frontend is accessing the slave. Replication poll interval is 1 hour. All is fine so far, but now as the traffic grows, the CPU load on slave is really high. I thought the best thing would be to add a second slave to the master and let the web servers connect via existing load balancers to the two Solr slave machines. I think that the two Solr slaves will handle their replication independently and each slave will poll the

I setup an EC2 instance with MySQL on EBS volume and setup another instance which acts as Slave for Replication. The replication set up was fine. My question is about taking snapshots of these volumes. I noticed that the tables need to be locked for the snapshot process which may cause inconvenience for the users. So, my idea is to leave the Master instance alone and take a snapshot of instance acting as slave. Is this a good idea? Is there anyone out with a similar setup and could guide me in a right way? Also, taking snapshot of slave instance would require locking of tables. Would that mean

For a project exisitng in github.com private repository, I am setting up gerrit code review. I am using the gerrit's replication plugin to keep the gerrit repository in sync with github.com. But if someone commits (say commit-a ) and pushes directly to github.com, the commit-a is overwritten in github.com, when gerrit does the replication process (because, it replicates only the things in gerrit mirror). But I want to implement a 2-way sync. Something like, whenever a push is made to gerrit, it has to check github.com and update its mirror with new code from there and then to continue the