Hi I have an incident history table that doesn't have a primary key. It is provided by a 3rd party so I don't have much of a choice there.
it has a clustered index on the incident id (which is unique on the table where the data originates) and a modified datetime. But without even looking I suspect that the incident id and mod datetime don't necessarily have to be unique.
The originating table is the source for a subscribed replication table. The ultimate would be for the subscribing db to be the recipient of something like a replicated history table as well.
do I have any options? I think one option is to set up a separate db (I heard log shipping cant go to a db that is enlisted as a replication subscriber) where log shipping would take place but I've heard log shipping is voluminous. and if the source of log shipping is the same tran log i'm used to seeing, i suspect the source is recovery full and therefore going to be much more voluminous than a recovery simple db source.