New answers tagged

0

What you are looking for is called Transactional Replication, which is very commonly used and a good solution for avoiding contention on a transactional database. There are three databases in a transactional replication system, which are the publisher, the distributor and the subscriber. The publisher is the source database, the distributor is where all ...


1

If you were referring to Database Mirroring when you say mirroring (as opposed to SAN mirroring), then don't. It has been deprecated since 2012 now so it is a potential candidate for complete removal in the future releases. Go with Always On Availability Groups. The difference in DBA overhead should be mostly the same. What is different, IMHO, is the ...


2

I would recommend you to use Always on availability group for server reasons. Database mirroring is deprecated as of SQL Server 2012 and will be removed on the future versions, so it is better to not use it on a new developments AOA group will give you a feature which you cannot get it on mirroring. Using AoA group, is like using a combination both ...


0

When you do a failover, a role reversal happens i.e. your primary becomes secondary and your secondary becomes primary. ALTER DATABASE [yourDatabase] SET PARTNER FAILOVER GO Doing so, only the role reversal happens (this is what happens when you initiate a failover using above command) and mirroring direction is reversed - principal becomes mirror and ...


3

I'm not sure I understand, you state you are going to use mirroring, in standard it is still available so why can't you use that? Or is the question that is there anything else available? You can also use Failover clustering in standard edition, the limit is you can only use 2 nodes but I don't see that as an issue for your request. Also, if you are using ...



Top 50 recent answers are included