From my understanding, normally transactional replication is used to create a 'mirror' copy of a database. However, I need to use it because it is the only method that does 'near-real-time' updating of the replicated database. My problem is that I need the replicated database to hold more information than what is on the original.
The original (short-term) database will have one month of records in it and the replicated (long-term) database will have that month plus the previous 11 months. How do I program the replication, so that when I delete a days records from the short-term database, I don't delete it from the long-term?
The purpose of this is that the long-term database is both current and archived data and the users will do all their retrievals against the long-term database.
Also, if it makes a difference, only INSERT and SELECT will be used with the long-term database. INSERT as part of the replication and SELECT by the users retrieving data.
I've looked through the Books-on-Line and can't find any information.
The original (short-term) database will have one month of records in it and the replicated (long-term) database will have that month plus the previous 11 months. How do I program the replication, so that when I delete a days records from the short-term database, I don't delete it from the long-term?
The purpose of this is that the long-term database is both current and archived data and the users will do all their retrievals against the long-term database.
Also, if it makes a difference, only INSERT and SELECT will be used with the long-term database. INSERT as part of the replication and SELECT by the users retrieving data.
I've looked through the Books-on-Line and can't find any information.