Tag Info

New answers tagged

2

Firstly I should say great question usr. Sean, Robert and Max have both correctly stated that due to the re-negotiation between the Primary and Secondary, that the correct LSN is always resolved so that there is not possibility of any discrepancy in that scenario. In response to the discussion with Shanky, in Synchronous mode, the Commit first has to occur ...


1

The issue you're running into most likely has to do with your users becoming orphaned on failover. Even though you're using the same logins, the SIDs are different, and don't match up with the users in the database. Basically, you need to recreate the user exactly as it is on server A. You need to do a CREATE LOGIN with SID = xxx that will create an exact ...


0

I have this script I generally use before I need to DETACH a database. it tests for mirror too. USE MASTER GO --=========================================================== -- before detaching the database -- see what files it has and where they are located -- checks mirror and replication -- database must not be part of mirror (neither as principal nor ...


2

How can it automatically change host of one if the other one was dropped ? From the client application side, your application connection string should use FailoverPartner pointing to secondary or mirrored server. If you connect with ADO.NET or the SQL Native Client to a database that is being mirrored, your application can take advantage of the ...


2

Automatic failover requires a witness. See Database Mirroring Witness: To support automatic failover, a database mirroring session must be configured in high-safety mode and also possess a third server instance, known as the witness. The witness is an optional instance of SQL Server that enables the mirror server in a high-safety mode session to ...



Top 50 recent answers are included