I have a server that was named "AlienDB" running SQL Server. I renamed the
server to "StagingAlienDB1" and now I am having problems configuring
replication.
When I try to do anything such as create a new Publication, SQL Server

Hi NG
Please forgive the length of this post, but I feel the background might have
some bearing on a possible solution.
We had a server running Win2003 + SQL 2000 SP3a that was acting as a

I enabled Replication: agent failure alert and I am try to test it. What do I
do to make sure that the alert will be fired when replication fails? What can
I do to manually test it?
Thanks

I am using SQL Server enterprise 2005 SP 2 as Publisher and subscriber
with Transactional Pull replication.
From last 2 days I am facing problem, Replication current activity status
show “Excellent” but the data is not publishing over to subscriber.  When I

I am trying to replicate a SQL Server 2000 Database
over vpn - The Distributor database in on Windows XP
and Subscriber on Windows 2003 server
I am running the subscriber but it fails with

I am a newbie to SQL replication so please be kind. :-)
I have read over chapter 7 of "Microsoft SQL Server High Availability"
available at:
http://downloads.techrepublic.com.com/download.aspx?docid=173142

When setting up security access between a publisher and subscriber, what
needs to be done?
I can't find a checklist of things to do when setting up connection and
access details from a publisher to a subscriber - is there something online

After migrate SQL 2000 replication to SQL 2005, by script and have maked some
changes, like drop some publications and have added many articles in one,
this message has appered so often:
Replication-Replication Distribution Subsystem: agent (null) failed. The

There was a replication problem between db1 and db3. The scenario is that a
table was added with more than 254 nos. of columns. An error
[Error 2757: RAISERROR failed due to invalid parameter substitution(s) for
error 20068, severity 16, state 1]

We have transaction replication set up in SQL 2K environment . It's simple
SQL 2k publisher to SQL 2K subscriber (both Enterprise). It works fine but
some times(once a week or so) we get error message "Could not allocate space
for object 'MSrepl_commands' in database ...

Dear There,
We just start the transaction replication for the database few month back.
Due to the heavy transaction on the database, we schedule daily log file
trancation before the daily full db backup happen, however, we found the log

I have an ASP.NET applicaiton that relies heavily on a replicated
database.  I would like to report within the application but I've been
unable to find a way to determin replicaiton latency.
Does anyone know of a way to programmically determine the time

SQL 2000 on 4 servers (distributor and 3 subscribers).
I deleted about 3.5 million records in a table on the distributor. One
subscriber got all of the deletes fine. The order 2 are getting an
error:

I deleted 3.3 million records out of a table on the distributor. They
merged correctly to one subscriber but the other two aren't getting the
deletes. Since the only deletions on that table would be the ones I did,
can I run the following with no adverse effects:

I had transactional replication working perfectly (well I thought so)
until recently.  The published database is very large (around 100GB).
Replication occurs over a relatively slow WAN link and is for disaster
recovery purposes.  Both servers are SQL Server 2000 SP4.