I have merge replication with a central publisher/distributor and 6
subscribers with anonymous pull subscriptions (laptops).
For this example lets say I have table1 (T1) and table2 (T2) joined with an
enforced 1 to many relationship.

If the logreader stops (separate distributor server from publihser) and
cannot connect to the publisher for - let's say - 4 hours, is that data lost
or will the transactions to be replication still be in the tlog? and
replication will catch up - in total (including the 4 hours ...

I have transaction replication set up and I want to set up a report to check
whether or not my replicaiton is up and runninr. Can someone suggest the kind
of queries I can run in Publisher, Distributor and Subscriber to check if
Replication is up and runnin or not.

Im getting the error below on my Distribution Server.
"Error at parameter 1 during datastream processing of parameterized command."
I followed the article below and configured the Distribution to log the
error on a text file.

Does the snapshot agent have to run if I already have a copy of the database
on the subscriber? We are doing a push subscription on transaction
replication.
I don't remember it running before, but today it is.

How to resolve in this problem in transactional replication
Could not drop object because it is referenced by a FOREIGN KEY
constraint
Thanks  in advance

Hi to everyone.
We are a small company that cannot afford having a cluster (low budget).
Instead, we are looking for alternatives to have two SQLServers, one of them
configured as a secondary server, so if the former must the put offline

I am planning a new deployment of SQL Server 2K. The scenario has a SQL
Server at our co-host facility to support our ecommerce activites and a SQL
Svr at our manufacturing facility to support our order fulfillment
activities. The ecommerce datbase is a subset of tables from our

We are load testing one-way trans repl by replaying a profiler trace on the
publisher.
The subscriber was restored w/ a backup.
Distr agent failing w/ foreign key constraint errors.

here is my question:
I have a two SQL servers X and Y.
X is the prodcution server and Y is a standby of that server at remote
location for the disaster recovery purpose.

Publisher /distributor - same server SQL Server 7.0  SP 4
Subscriber - Oracle 9.2.0.3.0
After configuring Oracle subscriber whether as a linked server or a system
DSN, I run the distribution agent and get the following error message:

Which third-party synchronous replication software are you using?
I googled and found Veritas Volume Replication, NSI Doubletake, among
others.
K.-

Is it true that log shipping is only for a readonly secondary server?
Thanks,
Gus

Using transaction replication on Sql 2000 Server SP3  I have setup server A
as the Distributor and Publisher. Server B is the subscriber but keep
getting this error message on the snapshot agent for the publication.
"The process could not bulk copy out of table