We are getting problems with synchronising a client. It was initially
synchronised with the server but the publication had to be dropped and
recreated and since then we have not been able to synchronise. We have
dropped and recreated the subscription on the client and on the server

I would like to hear your input on interesting system design question which
I am breaking my head on.
Here is the situation:
we have 2 manufacturing facilities and 2 related front end db servers taking

I am trying to test peer-to-peer replication. Going to BOL, finding:
How to: Configure Peer-to-Peer Transactional Replication (SQL Server
Management Studio)
#3 says:

I have a general question about merge replication: is it possible to have
several replications on one database and to distinguish in my application
between those replications? something like:
if (user.type == "1")

Is there any way of looking at the commands in the distribution
database that have not been applied??

Is there any sql command that I can use to check replication latency and
others that are related to replication healthy? Right now I need to launch
replication monitor to check, which is slow. I need sql commands to check in
order to be quickly. Thanks.

We have a large vendor applicaiton database that we replicate to
another server for reporting purposes.  We have an internally
developed applicaiton that uses that replicated data.  In the past
we've denormalized the data needed  into seperate tables to speed the

I have a merge replication on SQL Server 2005 and SQL Express using web
synchronization.
I have a publication with parameterized filter.
I have created snapshot with all initial possible criteria.

We have an existing SQL 2005 merge replication publisher/distributer. Is
it possible to have a SQL 2008 subscriber to this publication?

I just installed a new server with SQL Server 2005, and am trying to set up
replication.  When I try to add a new publication with the New Publication
Wizard I receive the following error:
New Publication Wizard encountered one or more errors while retrieving the

We have an application with SQL Server 2005 Workgroup edition awaiting
upgrade to Standard edition and have a limit on the number of
subscribers of 25.
We need to drop some of the existing subscribers to allow new ones to

I have log shipping that cause error:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set
terminates at LSN 133178000000753800001, which is too early to apply to the
database. A more recent log backup that includes LSN 133179000000894500001

I'm not familiar with replication and have a couple of questions about it to
see if it's the way to go or not.
The 2000 server has a third party app that needs updated customer info from
the 2005 server every 30 mins.  The 2000 server would update the data in the

We have transaction replication setup between two servers. Today an article
was added to the replication and it showed up on subscriber but the
replcation monitor had following error at the distribution agent. Log reader
is working fine.

I have two servers, SQL00 and SQL01B.  I have both set up with pull subscriptions from SQL20.  I want to remove SQL00, the current production server, from service and rename SQL01B to SQL00.  Has anyone done this sort of thing or know if I should anticipate issues.  My intention ...