Is it possible to setup merge replication between SQL Server 2000
(Publisher) and SQL Server 2005 as (Subscriber)  because when i try to
setup, it gives me a message that the "subscriber version cannot be higher
than the publisher version" ? If transactional replication works, ...

I cannot find where to change the 'schhedule' in SMS 2005.  I can go to
EM & do it...by finding it in the distribution agents.
Do I have to navigate to the job in the SQL Agent->Jobs folder??
Larry...

After working for about 30 minutes (delivering the snapshot) the replication
failed
I checked the Session details of the subscription and I found Action Message
saying the 'The process could not deliver the snapshot to the Subscriber.'

so
Im coming to end of my replication testing and im really wondering if I want
to do this. some basic problems that im noticing:
if i create a new table / SP I have to re-run the snapshot agent to create

It may be simple but I find it difficult to delete a subscription. When I
right click the subscription I don't get this option and I can only delete
it by deleting the Publication

All servers SQL2000 Std Ed., sp4
Transactional Replication
Publisher in Hong Kong, distributor in Calif - subscriber in Calif
LogReader & Distr. agents on 2 minute schedule.

I am looking for a way to avoid the option of 'Yes initialize the Schema and
the data' (which I suspect is the source of some problems) when I create a
new subscription
Thank you,

Since I had some problems setting Push Merge Subscription I tried to 'Run
Agent at Subscriber' while setting it I clicked on 'Verify Subscriber'
button and I got the following error:
Server xyz is not prepared to run the offloaded agent

I am still struggling to delete a subscription so I can set another one to
that server
I believe that normally that would be listed in the Properties Page of the
Publisher, but it doesn't

Hello,
I need to automate the replication from live server to test server (i.e
weekly backup of a live server followed by restore to the test server).
Any pointers would be greatly appreciated.

Hello, I am not a sql server programmer.
I have a database which already has a publication set up, which sends a
bunch of tables to subscribers. Everything was okay, but now I need to
publish two more tables. These tables contain columns which are user

I am looking for a workable alternative to using GUIDs as the PK in tables
that are included in a replication system where there are multiple remote
locations and a central database with all the remote and central databases
requiring to be synchronised, so there is two-way ...

I have three SQL 2000 servers, with transactional replication between them
(27GB database, +2GB/month)
SQL1 -> SQL2 -> SQL3
SQL1 is a publisher+distributor

I'm trying to add a column to my peer to peer replication.  According to the
help I've found:
Adding Columns
 a.. To add a new column to a table and include that column in an existing

I'm using a replicated SQL Server 2005 database on my server and a SQL
Server Everywhere CTP (v3.1) database as my client app. Everything works
fine (including sync) until I add a row to a table on the subscriber
(client). Upon the next synchronization I get the following error: