Please start any new threads on our new site at http://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 High Availability (2008)
 Mointoring Mirroring in sql server
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

anoop_mig25
Starting Member

India
20 Posts

Posted - 01/07/2015 :  06:28:36  Show Profile  Reply with Quote
Hi friends



basically my question is how can i determine whether transaction executed on primary server would be applied on mirror server or not .

I mean in log shipping with restoration job and redo-undo file one is sure that particular transaction would get applied

But how is this mechanism implemented in mirroring ?????

I mean there is SEND and REDO queue in mirroring purpose but there is is size of queue , oldest unsent transaction , current sent rate and restoration rate etc


but from this counters how can i pull out data whether my transactions is shipped or applied in mirror instance of not

Regards
Anoop Pandey

robvolk
Most Valuable Yak

USA
15732 Posts

Posted - 01/07/2015 :  06:53:59  Show Profile  Visit robvolk's Homepage  Reply with Quote
Database mirroring is continuous log shipping. If you use high-safety mirroring, the transactions must be successfully sent to the mirror before they are committed on the principal. (They may not be redone immediately, but they are at least hardened in the mirror's log).

You can query sys.database_mirroring DMV to get information on the log sequence numbers (LSNs) that have been sent, hardened, and flushed to disk:

http://msdn.microsoft.com/en-us/library/ms178655.aspx

It will also provide information on mirroring state, in case your mirror is suspended, disconnected, etc. If you set up the mirroring monitor job:

http://msdn.microsoft.com/en-us/library/ms403582.aspx

You can query historical mirroring status with the following:

http://msdn.microsoft.com/en-us/library/ms366320.aspx
Go to Top of Page

anoop_mig25
Starting Member

India
20 Posts

Posted - 01/07/2015 :  11:24:41  Show Profile  Reply with Quote
quote:
Originally posted by robvolk

Database mirroring is continuous log shipping. If you use high-safety mirroring, the transactions must be successfully sent to the mirror before they are committed on the principal. (They may not be redone immediately, but they are at least hardened in the mirror's log).

You can query sys.database_mirroring DMV to get information on the log sequence numbers (LSNs) that have been sent, hardened, and flushed to disk:

http://msdn.microsoft.com/en-us/library/ms178655.aspx

It will also provide information on mirroring state, in case your mirror is suspended, disconnected, etc. If you set up the mirroring monitor job:

http://msdn.microsoft.com/en-us/library/ms403582.aspx

You can query historical mirroring status with the following:

http://msdn.microsoft.com/en-us/library/ms366320.aspx




Hi robvolk thanks for reply and quote
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000