The database was created before I arrived. It is a very complicated database, and also a very poorly designed one in many areas. At this time my aim is to replicate to the backup server to automate that proccess (as opposed to manually copying backup files several times a day). Efforts to imporve / modify the database design must be done carefully as it is in full production. This would include changing the 'Not For Replication' flags on the tables to true.
I know that setting that flag would preserve the index numbering, but would not setting it precude the replication of the tables? I had not thought that.
>>I set up a new replication and upon initialization got the error:
>>
>>Could not drop object 't_account_xref' because it is referenced by a FOREIGN KEY constraint.
>>
>>I do not understand. Can tables with foreign keys not be replicated?? This would not make sense to me. Perhaps I am making another error.
>>
>>Any input is appreciated.
>
>Did you set the not for replication option to true?
Thank You
Rollin Burr
Politicians and diapers have one thing in common. They should both be changed regularly, and for the same reason.