"Hilary Cotter" <hilaryk@att.net> wrote in message
news:OBOUn8XpDHA.424@TK2MSFTNGP10.phx.gbl...
> your probably thinking about msrepl_transactions. This is the number of
the
> transactions in the distribution database since the last distribution
> cleanup agent was run and cleaned up applied transactions.
>
> To get an idea of your actual latency select
> substring(transaction_timestamp,1,10) From
> dbo.MSreplication_subscriptions on your subscriber database. It is
> immaterial whether it is push or pull.
>
> Then go to your distributor - on your publisher - it is immaterial if it
is
> push or pull.
>
> Do this:
>
> select xact_seqno, entry_time from msrepl_transactions
> where xact_seqno = 0x00016823000024930004 --this is the value I
> got from the above query.
>
> the entry_time is the time of last replicated command for that
> subscriber/publisher pair
>
> "Hassan" <fatima_ja@hotmail.com> wrote in message
> news:#g5plaWpDHA.2848@TK2MSFTNGP10.phx.gbl...
> > I came across some table or stored proc that tells the status of how
many
> > commands/trans are still awaiting to be pushed to the subscriber from
the
> > distribution db
> >
> > What is it ? Using SQL 2000
> >
> >
>
>

"Hassan" <fatima_ja@hotmail.com> wrote in message
news:#g5plaWpDHA.2848@TK2MSFTNGP10.phx.gbl...
> I came across some table or stored proc that tells the status of how many
> commands/trans are still awaiting to be pushed to the subscriber from the
> distribution db
>
> What is it ? Using SQL 2000
>
>