Hey. I've a few transactional publications. It fails with this error. When I
looked at the command, it's trying to insert a null in identity column. Why
does it do that? As of now, I've commented the update for the identity column
in the sp_msupd_logdevicebeacon. But now, if ...

I want to set up a replication between servers over the internet. I know
there are 3 ways to do this, using VPN,proxy server or TCP/IP (FTP). but I
don't know the advantages of each one. could you tell me what are the
differences between these ways in performance and security?

Can I use DISTRIB.EXE or REPLMERG.EXE  to force SQL Express to synchronize a
Pull Subscription on the SQL Express machine to the publisher (SQL Server)?

I have a situation where I have SQL Server 2005 as my Publisher/Distributor
and I have it setup to run Push Merge Replication.  The subscriber is an
instance of SQL Server Express.  Obviously SQL Server Express doesn't have
the means to force synchronization.  I do have it setup ...

I cannot set my server as a distributor. It keeps telling me "SQL Server
Agent on 'My Server Name ' currently uses the system account, Which causes
replication between servers to fail. In the following dialog box specify
another account for the Service startup account". I use the ...

We have a SQL2000 Publisher, and SQL2005 server doing Distribution and
Subscription. We're using transactional replication with push
subscription.
We've had this running reliably for 2 weeks with one publication with

Hey guys. I went to the Agent history for the distribution agent and it tells
me
'A total of 1 transaction(s) with 8 command(s) were delivered.'
Can someone tell me how I can check what was exactly done at this

Hi I have transactional replication on my server. If I need to restart the
Agent or Sql Server is there anything I should be aware of or is there a set
way to restart sql server or the agent. If I restart Sql Server while a
transaction is going on will there be any corruption or ...

I'm starting down the road of considering merge replication in SQL Server
2005 (via IIS/HTTPS) (as opposed to writing my own synchronization code and
communicating via Web Services).  The more I look into it, I'm feeling more
comfortable with it.

I'm wondering how well merge replication scales to a large number of
subscribers.  Where is the state of the merge sync relationship between the
publisher and subscriber stored?  Is it in the subscriber database,
distributor database, or in the publisher database?

Once a merge relationship is established, what happens when either the
publisher restores a previous backup, or the subscriber restores a previous
backup?  How is this handled?  Will the latest data will be restored from
the database that didn't crash?

When a subscriber has exceeded the retention period since the last sync,
I've heard that it can upload it's changes to the publishser then
reinitialize the subscription.  How is this upload handled?  Is this a
manual process?  Or is this case specifically handled by merge ...

Is it possible to create a publication entirely from within my application?
If so, are there some samples or documentation anyone can point me to?
Thanks in advance,
Terry

SQL Server verison on Publisher: 8.00.970
SQL Server verison on Subscriber: 8.00.970
An update proc containing two statements was issued on the subscriber. The
queue reader reports ODBC Error: Invalid cursor state.

Let's say TableA on a 2000 ServerA.DatabaseA has an identity key and I want
to transactionally replicate that TableA to a ServerB.DatabaseA (that is also
2000).  But here's the catch:  in the case of a significant outage on ServerA
I want to be able to repoint the web to ServerB ...