Advice needed: How to archieve feature with relational integrity?

Hi all!

what I need is an advice or conceptual solution.

In BMap working with SQLServer db, I have to move one feture (...WHERE ArchiveDate IS NOT NULL) in second table (archive table with same propreties). Feature has relational integrity with Annotation, child table where origin point of Text element is stored.

I'm thinking to create a trigger (INSERT, UPDATE) for every post from BMap which can check ArchiveDate property,  insert feature to second table and delete it in first. Everything is working fine until I have Annotation as child element attached to main feature. Sometimes Annotation can be attached to main feature sometime it doesn't.

Does anyone have an idea how to solve this problem using triggers?