In a merge replicated environment, is there a way to insert a record
in both the replicated database and the central database with the same
RowGUID and make them work replicated afterwards?.
I need to push a record to a device quickly, but once there it should

I have 2 simple tables merge replicated.
When I go to publication properties==>articles==>article properties, i see
that create clustered, nonclustered indexes, unique constraints are set to
true but ...

We have a database that we run on our server, and have now added merge
replication.  We have not had any performance issues on our database
until the replication was implemented.  The subscribers running the
database have no problems, but any workstation accessing the server

 I am in a situation that apparently does not seem workable the way SQL
server replication works, but I wanted to make sure I am not overseeing
something obvious as this scenario should be somewhat common in big
replication scenarios.

I want to make this SQLExpress clients Agent use the "Slow connection"
profile. Setting slow profile on the server I assume does nothing for me at
all???  I assume that because the Agent runs on the client. Correct?
So does a SQLExpress install have "agent profiles" given it ...

I'm a little confused on how replicating a SP to update a table works versus
using a trigger. How does the SP know to fire when an update to the table
has been made. I'll report my old thread below to show you were my confusion
is.

I am implementing replication in 3 computers: publisher, distributor,
subscritor. But in moment the suscription i have this message: the operation
could not be performed because OLE DB provider 'SQLNCLI' for linked server
'i16e' was unable to begin a distributed transaction. ...

We have a SQL2005 server running on Windows Server 2003 R2.
It has been running fine and replacting data for almost a year now.
Last Tuesday June 17 a number of microsft updates were applied to the server
- including several SQL Server updates.  After the patches all seemed well.

SQL server 2000 log shipping was working fine.  All service packs
up-to-date.
Suddenly, my standby database decided it was "loading/suspect".
I removed all log shipping, but I couldn't do anything with the standby.  I

 I was wondering if there are tools around that would allow me to monitor a
number of publishers and retrieve information such as "in synch with x,y,z",
"last updated on", and stuff like that. I am looking for something different
than the SQL Server Enterprise Manager and ...

I am trying to follow the replication tutorial in books online, but
using my own two databases instead - both are on the same instance of
SQL Server 2005.
I get the error you can see at

I know replication isn't supported directly by SQL Server 2005, and
have setup merge replication over https with a W2K3 publisher and XP
subscriber to perform various bandwidth usage tests. I'm trying to
ascertain whether replication is a viable approach for my needs - at

   I am using the Windows Synchronizer with SQL Express. If I am logged in
as a Windows Administrator, I can see the subscription in the Synchronizer,
but if the user is not a Windows admin, the subscription is not available to
be synchronized. If I make the user an admin, then ...

I have the read the many posts regarding this topic, but have not
really found an answer yet.
I have SQL 2005 SP2 on three different servers running transactional
replication.  I have an existing publication to two subscribers with

We have a customer that is replicated (publisher plus 3 subscribers) -
one of the subscribers received an error 823 on their DB. I stopped
MSSQL Server, copied all files to another directory, created a new
directory, copied the files back, and tried to attach (thinking that if