SqlServer Begin's

Are used for rewinding transactions and keeping a track of the transactions VLF are created depending on the number of active transactions combined with transaction file growth Ex. If the file growth was less than 64mb there will definitely be 4 VLF files in the log There will always be at lest one record with Status = 2 ; which will signify the active transaction on the VLF   When there are inactive transactions and if a Checkpoint is issued the older VLFs are reused  The parity column will help to identify if the log has been reused and the possible number of times the log was reused ( it will start from 64 and increase 64 every time it’s been reused) Sometimes you would find VLF’s without any usage (where FSeqNo , Status and Parity = 0) , these VLF are added by the subsystem in case a roll forward or roll back is required( this is due to the many number of active transactions in the log) Clearing the log does not mean that the VLF’s would reduce but it would reduce to hold

I wanted an easier way of monitoring the status of replications without having to use the “replication monitor”. Following are three procedures that’s available in sql server to assists in getting information pertinent to the status of replication ·         Get the Publisher status USE distribution GO sp_replmonitorhelppublication @publisher = null, @publisher_db = null,    @publication = null, @publication_type = 0 Results n        Look for the status where it can be any one of the following 1 = Started , 2 = Succeeded , 3 = In progress , 4 = Idle , 5 = Retrying , 6 = Failed Returns : current status information for one or more publications at the Publisher.The procedure is executed at the Distributor on the distribution database.   Resources http://msdn.microsoft.com/en-us/library/ms186304.aspx ·        Get the individual subscriber status USE distribution GO sp_replmonitorhelpsubscription @publisher = null,   @publi