I'm running a syncornized mirroring setup using a witness on our LAN.
Since we don't use a domain controller, we use certificates for outbound and
inbound mirroring connections.
We're using sql server 2005 SP1 standard edititon on all machines.

We have a merge replication setup in SQL 2000 that synchs with 2 laptops.  I
need to add a new table to the database that will be included in the new
subscription as well as a change (adding a column) to a table already in the
publication.  What are the steps I need to take to ...

I currently have a VB6 app that I am rewriting.  I am now using Visual
Studio 2005 and the new app will be a windows forms smart client.  I am
using SQL Server 2005 Compact Edition as the local database.  I have SQL
Server 2005 Enterprise Edition setup as a merge replication ...

I execute a sp_addscriptexec because I wanted to create a trigger, but it
already exists in some of the subscribers. So, I get the following error:
"....\Microsoft SQL
Server\MSSQL$SQLSERVER2000\ReplData\20061213182034400\script_trigger.sql'

my sql server has sp4 installed. i have two databases, D1 and D2. And the
transaction replication copys table D1.T1 to D2.T1 at 1:00pm everyday.
the problem is:
when some applications are continuously using table D2.T1, i mean those

I have a database in SQL2005 is adatabase of 52 tables and is Merge
Replicated.
Currently 12 Handhelds use this set ... but in the futere we will go up
to 60 handhelds.

  I created 2 windows user named PublishUser and ReplSnapAgent with less
previllege. Ran SSMS using PublishUser and created snapshot publication.
Used RepSnapAgent user as Snapshot Agent. I got an error saying
SQL Server could not create publication 'Product'. (New Publication ...

I have two questions:
1. about sp_adddistributor - in the case when a remote distributor is being
used does it have to be run both at the publisher and at the distributor?
2. about sp_addsubscriber - where does it fit in the chain of replication

All,
In Transactional Pull model, is there a way from any storedprocedure to
get notification from the distribution agent that the initial snapshot
has been applied on the subscriber?

How to move 50GB of  Publication Database to new Hardware( New SQL Server)
quickly without loosing replication inforamtion.
Replication Type : Merge
OS : Windows 2003 Server

1. Can we replicate tables with no primary Key. Will Sql server add some
type of constraint in tables.
2. Can we replicate Bitmap/Blob data.
What kind of replication is suitable for these scenario

Things I got to work
SQL2K, Merge Publication -> SQL Everywhere (I used the interface in SQL2K5
to do this Subscribe,  can anyone show me how to do it in C# 2005 code???)
SQL2k Merge Publication with Dynamic filters(i.e SUSER_SNAME) -> To Another

I recently setup merge replication and for each subscriber I add and try
and synchronize I get the following error message:
"The Process Could Not Log Conflict Information"
When I view the details of the error it states the following:

please help !
i don't know why my store procedure of the transactional replication will be
recreate  the store procedure everyday.
After that i will get the error like below:

How i can stop the replication to run thru the transactional update, insert,
delete without recreate the other new store procedure?