Tag Info

New answers tagged

0

I had the same issue with configuring mirroring as my partner server was located in a different hosting center with no cross connect. What I had to do was monitor my database usage. This then showed me the quietest time of day to do the Full and log backup. My company generally has about 20000 transactions every min. I ended up having to configure my ...


1

After you take your transaction log backup and restore it on the mirrored pair, you might have taken more transaction log backups. If so, try to catch up on the backups then init the mirror. At that point all the old transactions that are not replayed with be queued up and you will endure a DB_MIRRORING event on your log file which will stop the ...


0

Since Mirroring operates by shipping over a live transaction log to the secondary servers, you'll need to start a new mirroring session. Your secondary database has been out of sync for a week and unless you've managed to maintain a transaction log on the primary that spans that entire time (hint: you haven't), you'll need to start with a fresh backup on ...


4

This is documented here on BOL: Thread Usage By Availability Groups. For redundancy purposes, here is the breakdown: 3 to 10 shared threads (but can increase depending on primary replica workload) (primary replica) 1 log capture thread per primary database (primary replica) 1 log send thread per secondary database (secondary replica) 1 redo thread for ...


1

I have personally had experience with Transactional Replication. In my case, I configured the Distributor at the Report Server, and then created the Publication on Live server to be controlled from the Report Server. The Subscription from the Report Server worked perfectly. With this configuration, I was successfully able to replicate data from the Live ...



Top 50 recent answers are included