Replication transcations

Hi All
I had stopped transactional replication for about 5 hours and now i have
restarted it. The replication is so slow. How can i calculate how many
transactions are left to be replicated? Both the log reader and distribution
agent are running although at times they time out.. I have tried to query the
table MSrepl_transcations but nothing makes sense to me.Thank you in advance.
query select * from distribution.dbo.msdistribution_status or execute
sp_browsereplcmds in the distribution database.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"MittyKom" <MittyKom@.discussions.microsoft.com> wrote in message
news:54BB99E9-1F10-4AE4-8747-3B99F27DE83B@.microsoft.com...
> Hi All
> I had stopped transactional replication for about 5 hours and now i have
> restarted it. The replication is so slow. How can i calculate how many
> transactions are left to be replicated? Both the log reader and
distribution
> agent are running although at times they time out.. I have tried to query
the
> table MSrepl_transcations but nothing makes sense to me.Thank you in
advance.

Replication problems

Hello guys, we have a problem with the merge replication in my company, the
downloads replication is very very slow all times, the upload process is
very fast, but, when the download process starts, then the suscriptor crash
and the locks begins to appear in the database. The processor usage is 100
% and the disk activity is elevate too.
Excuse me for my bad English, please I need help, I don't know wit this
Regards
Its hard to say what is going on. You should review this white paper.
http://www.microsoft.com/technet/pro.../mergproc.mspx
and
http://www.microsoft.com/technet/pro.../mergperf.mspx
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jesus Brito" <jesus.brito@.sigosa.com> wrote in message
news:O04tJibdFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hello guys, we have a problem with the merge replication in my company,
the
> downloads replication is very very slow all times, the upload process is
> very fast, but, when the download process starts, then the suscriptor
crash
> and the locks begins to appear in the database. The processor usage is
100
> % and the disk activity is elevate too.
> Excuse me for my bad English, please I need help, I don't know wit this
> Regards
>

Replication is very Slow

When we try to replicate the database from one server to another server it is very very slow...

Then we assumed that the Indexed View may cause this issue.. But we didn't check by removing the index & replicated it..

Can any one suggest me for the following Qs..

Is it Indexed View really bad on Replication(Main Table)?

What is the alternate & best solution for Indexed Views?

Is Covered Index solve the Indexed View issue?

Is Convered Index wont create the Replication issue?

Is it good idea to disable the Index on View on Replication and re-create the index?

Pls guide me on this issue..

We are Using SQL SERVER 2000 Enterprise Edition

Modifying Indexed views are slow in general, and not necessarily a replication issue. When modifying indexed views, you're basically doing two writes for every operation - one for the view, one for the underlying tables, plus double the index maintenance.

You can read some basic information about replication and indexed views here - http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx.

You didn't say exactly what is slow, so what you should do is compare performance impact of ins/upd/del statements to the indexed view at the publisher database, with and without replication.