I am using trasactional push replication on 2005.
So, first I do this:
EXEC sp_addarticle
@publication = N'azDSS',         -- Change value with the name of the

Does anyone know if MSDE can use replication of any kind?  I'm looking to
gather up many tiny databases and pull them into a larger 2000 box that is
Processor licensed.
I read that you can set up replication manually using scripts, but the

I need to take backups of all DBs in the server into another serve, which
should be done automatically once a particular period of time(say 30 mins or
2 hrs or 5 hrs etc..).
Please help me to do so with step by step explanation. iI am new to SQL

I am getting the following error when trying to insert a record into a table
at a subscriber.
Table '[dbo].[Customer]' into which you are trying to insert, update, or
delete data is currently being upgraded or initialized for merge replication.

I have 3 SQL server 2000 involved in Replication which will need to be
upgraded to SQL 2005
Publisher
Distributor

Hi i need to know how would it be possible to configure SQL 2005 and 7 to
replicate with each other.
SQL 7 will need to be the publisher and SQL 2005 will be the subscriber. SQL
2005 will not update back any data to SQL 7 but just read the changes made

Other than the following constraints on "Concurrent Snapshot Processing", is
there any reason NOT to check the "Concurrent access durning snapshot
generation" option?
Known Constraints:

Snapshot Error Details:
-----------------------------
Invalid object name 'sysarticles'.
Invalid object name 'sysarticles'.

I just talked to Microsoft and I was told to do push subscriptions instead of
pull, to run the distribution agents on the distributor.  I have come across
different resources that say otherwise...  What is the best approach with a
distributed topology.

We currently have Merge Replication setup on a Sql Server 2000 running on
Windows 2000 Server as publisher. Same configuration servers (45 units) are
acting as Subscribers.
We want to replace one of our subscriber servers and run on Windows 2003

I'm hoping for some insight into this problem. We have Merge
Replication setup over FTP and has been working without issues. The
last database update we generated a new snapshot and has cause problems
since. The snapshot generates fine. When we synchronize uses get the

I'm working on setting up replication on a database in SQL 2000 and get the
following error:
Implicit conversion from data type text to nvarchar is not allowed. Use the
CONVERT function to run this query.

Yesterday, we attempted to add a new table to an existing publication.
We then created the table on the subscriber and populated it manually.
We expected that replication would then take over the data flow to this
table.  This morning, I found that the log reader had failed with the

I have a merge Replication database with 50 tables.
Almost all my tables have identity columns.
Now the subscribers of this Publication database cannot "Insert" or
"Delete" data on tables that have identity columns.

I am trying to work out what the difference is between the above and merge
replication. Does anyone know what the difference is?