![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
How about creating the foreign key references as NOT FOR REPLICATION? See Books Online for more information. -- HTH, Vyas, MVP (SQL Server) http://vyaskn.tripod.com/ What hardware is your SQL Server running on? http://vyaskn.tripod.com/poll.htm "Gregor" <g_heidinger (AT) hotmail (DOT) com> wrote in message news:uRWFJREYDHA.1872 (AT) TK2MSFTNGP12 (DOT) phx.gbl... We are replicating data from one SQL database to a different SQL database (on the same server, MS SQL 2000). For this, we use Transactional (Push) Publications and DTS packages (with data driven queries and ActiveX script). In the 'old' database, we have one table witch data goes into two tables in the 'new' database. These two tables have a relationship (table 1 = Header, table 2 = Details). We use for each subscription / table in the new database a publication with a DTS package (the articles in the publications are partitioned horizontally (only active records are included)). If the state of a record in the 'old' database is changed from 'not active' to 'active', it is in the partition and must be replicated via the two publications. The problem is that the publication of the details is run first, resulting in an error, because the details need a reference to the header (that is not yet in the 'new' database). How can we specify the order of the publications? Thanks, Gregor. |
![]() |
| Thread Tools | |
| Display Modes | |
| |