New answers tagged

0

Recently, we set up log shipping to an off-site server and it seemed to be working great. The LSBackup job runs every 15 minutes. You should change the maintenance plan and just take full and diff (if required). Since logshipping is taking log backups every 15 mins, you dont need hourly log backup. but my question is do I need to remove all log shipping, ...


2

First of all, thanks to @Dan Guzman for his inputs, somehow it sparked something in my head. :) I found out the reason for the break in the LSN chain! As I mentioned, the chain breaks after a backup is made to 'NUL', and I just came to know that 'NUL' is a sort-of file system, where data is written to it but then deleted afterwards. So obviously, if a ...


3

Is there a reason, other than tradition, that you need SQL01 to return to being the "primary"? You could do just a single flip, and skip the confusing mess of short-term log shipping: Original state: Primary database on SQL01, set up to replicate all tables to SQL02. When you do maintenance on SQL02, replication will queue up changes in the distribution ...


4

Separate from your Replication solution, could use a Failover Cluster Instance or Basic Availability Group for HA of your publisher. Or, if you have a stomach for obscure replication solutions, you could implement Bidirectional Transactional Replication, which is similar to Peer-to-Peer replciation, but older and available on Standard Edition.


0

I have not used Amazon Cloud for my servers, but assuming the replication works , Replication will be a good solution for your requirements. Just need to be sure that your tables have a primary key. In the case of replication since you can choose which tables to replicate, it could help for your performance (log shipping the whole DB vs replication just ...


Top 50 recent answers are included