Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 DB Replication Does Not Replicate Keys

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2001-11-19 : 10:38:16
David writes "I have searched through BOL, MSDN, the internet, read through "Professional SQL Server Programming" and posted at a few discussion boards but I have not found out how to do this or something simply saying that it can not be done.

Goal is to have a mirror DB of our production DB including the Keys.

We are using 2 SQL Server 7 servers on Windows 2000 both with latest service packs and I want to replicate a database from one of the servers using transactional replication and have the keys also be replicated. DB is approximately 50 tables.

The database published on Server A is pushed to Server B.
Distribution is done on Server A.
Replication is transactional.
Distribution is continuous.

When using a snapshot to initialize the schema on the subscribing DB, replication works but the keys will not appear on Server B.

If I initialze the schema on the Subscriber by backing up the DB from Server A and restoring it to Server B then start the replication (after fixing the user issue) or use DTS to move the DB, I get a message from the Distribution Agent similar to this...

Error: "Could not find stored procedure 'sp_MSupd_Employees'."

Last Command: {CALL sp_MSupd_Employees (NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,N'98111',NULL,NULL,NULL,NULL,NULL,NULL,NULL,1,0x000400)}
Transaction sequence number and command ID of last execution batch are 0x0000001B0000002F000A00000000 and 1.

In this example I was trying the same thing with a Northwind Database for a test with 2 SQL 2000 servers on Windows 2000.

Same thing happens with SQL 2000 servers trying both methods with any DB.


I have found nothing saying that I can not replicate a DB having keys on both the Publisher and Subscriber and have found nothing about the above error. Please let me know if there is something I am mising or if what I am trying to does simply is not feasible.


Thanks,

Dave"
   

- Advertisement -