Dear Professional,
I would really appreciate if anyone of you can guide me, I have 20 GB of
database and I want to apply merge replication,
What would be the best approach?

Windows 2003 w/ SQL Server 2000 merge replication
Is there a way to have the synchrnoziation process restart after a set
amount of time when an error occurs - such as general network failure or
deadlock error?

I've received conflicting information from Microsoft personnel so thought I'd
see what some thoughts here are.
In summary, we upgraded a server from SQL Server 2000 SP4 Standard to SQL
Server 2005 SP2 Standard.  This servers main purpose is to handle alot of

I would like to know which one is the best replication method to be
able to fully automatically replicate a db even when I add new tables
and make any kind of transactions.
Thanks a lot

What do you think of the following scenario?
Replicate from a Sql 2000 server to a new Sql 2005 server
and then replicate from the new Sql 2005 server to a new Sql 2005 reporting server.
If this makes sense, I am thinking I can move my db's in piece meal rather than 1 big move.

1.    Can we create merge replication through script including distribution
database.
2.    I am wondering if one of the box (either subscriber or publisher) goes
down, what are the steps needs to follow.

I would appreicate if any one provide me Merge Replication Script, that will
create Publisher Database, Distribution Database and Subscriber database.
Please advice
thanks

I have a SQL 2000 database that I want to replicate over a slow WAN link.  I
was going to place the distributor with the subscriber.  Would that have a
significant impact on the performance of the Publishing database (OLTP)?
It's ok if the subscriber falls a little behind.  I ...

We have an existing merged replication schema that works well. One of the
tables is named audit. Currently this is a bidirectional transfer. However,
we want a new audit table that will transfer data from the subscriber to the
publisher

I'll start off by saying these questions were submitted to Microsoft and no
one can give us an answer without them doing a source code review.  Their
response was "these are internal BCP scripts that are used by SQL"....yes, I
know that....that doesn't help to explain why the ...

I have created Merge Replication and it worked perfactly fine. All the
tables and replicating fine.
I have created new stored procedure on Publisher but it's not replicated
into Subscriber. Can anyone tell me which command I have to used to make

When it is run the snapshot agent, this error:
The identifier that starts with 'PEDIDOS_FOR ) ))
                begin
                    insert into

We want to use peer to peer transactional replication to replicate a large
number of small databases between a primary and failover environment.  When
the number of databases hit around 40-50 we started getting replication
problems due to logread.exe and distrib.exe not starting. ...

Just want to confirm i'm going down the right path..
Using sql server 2005.
I want 2 machines to have a copy of the same database, with users
accessing either database, i want the 2 databases to be in sync the

The problem:
Every time I try to use Windows Synchronization to update the subscription I
get an error box with a title that starts with: "Synchronization Manager:
MOBSYNC.EXE"  and the message: "The proceedure entry point