Can someone help me with an archiving solution where a row in a table when deleted a trigger is raised and the row is moved to another table and under a archive database.
The archive table schema should be kept in sync with current table schema
feedback
|
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. See the FAQ for guidance on how to improve it.
|
You cannot setup triggers on table alterations. Perhaps you should look at archiving bin logs... instead of trying to archive deletes. Perhaps you should just deny deletes altogether... and simply have a "isDeleted" field. | |||
feedback
|