Easy SQL 7 Replication question

Hello,
I have replication b/w 2 SQL 7.0 SP4 servers over a t1
connection. The type of replication is non-immediate
updating transactional replication pushing 1 way.
Sometimes the t1 connection will die. When the connection
comes back up the SQL Servers begin replicating again.
What happens to the transactions on the push server during
the connection loss? Are they stored in the distribution
DB until the SQL Servers can communicate again?
Please advise...
Thanks,
Louis
Louis,
they are never lost - they stay in MSrepl_commands on the distribution
database until all subscribers have read them or they have reached the
Transaction Retention Period (assuming non-anonymous subscribers).
Regards,
Paul Ibison
|||I believe these commands will reside in the MSreplication_queue table.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" wrote:

> Louis,
> they are never lost - they stay in MSrepl_commands on the distribution
> database until all subscribers have read them or they have reached the
> Transaction Retention Period (assuming non-anonymous subscribers).
> Regards,
> Paul Ibison
>
>
|||Thanks for the help, Paul.

>--Original Message--
>Louis,
>they are never lost - they stay in MSrepl_commands on the
distribution
>database until all subscribers have read them or they
have reached the
>Transaction Retention Period (assuming non-anonymous
subscribers).
>Regards,
>Paul Ibison
>
>.
>
|||MSreplication_queue is probably also of interest, but Louis mentions he is
referring to transactions on the push server.
Cheers,
Paul
|||yikes, that's correct Paul.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OKCEZ$FWEHA.3892@.TK2MSFTNGP10.phx.gbl...
> MSreplication_queue is probably also of interest, but Louis mentions he is
> referring to transactions on the push server.
> Cheers,
> Paul
>

Easy questions about replication & Publication

Hi...
We have a SQL Server Std Edition that make syncronisation(merge
publication) with 100 mobile device.We create100 publications according to
our employees user id.We use articles with joins and user id for all
publications.The mobile devices make syncronisation over this publications.
Problem1:When I execute an insert or update statement in database , it cost
min 10 minutes for response.Last night I execute an update sql(for 10 rows)
at night.When i wake up morning,the transaction log is get full, and only 2
of the updates make succesfully.
Why database ddl operations get a long time to execute?
Problem2:How can I control transaction log automatically?
I'll wait for your answers..
Thanks...
answered above.
http://www.zetainteractive.com - Shift Happens!
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
"The_TOZ" <tunc@.te-mob.com> wrote in message
news:65A79B21-C9D6-498A-BC7F-3E2053C53EF3@.microsoft.com...
> Hi...
> We have a SQL Server Std Edition that make syncronisation(merge
> publication) with 100 mobile device.We create100 publications according to
> our employees user id.We use articles with joins and user id for all
> publications.The mobile devices make syncronisation over this
> publications.
>
> Problem1:When I execute an insert or update statement in database , it
> cost min 10 minutes for response.Last night I execute an update sql(for
> 10 rows) at night.When i wake up morning,the transaction log is get full,
> and only 2 of the updates make succesfully.
> Why database ddl operations get a long time to execute?
> Problem2:How can I control transaction log automatically?
> I'll wait for your answers..
> Thanks...