Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • I will be later moving this data to other storage. Also, by size of the DB, I mean size of live DB (to ease the process of re-storation, when needed). I don't plan to do it in sync fashion but my records are on the basis of parent table's status than the timestamp so, bulk deletes might not be of much help. In otherwise case (without triggers), I think I will have to find the dependencies (using reflection), create a dependency graph and perform ordered archival and deletion which sounds like little complex than the trigger approach. Any thoughts? Commented Nov 6, 2014 at 19:13
  • @instanceOfObject: well, I don't know your data model, and if you think triggers make things easier, then don't hesitate to use them. If you have so many tables you need to auto detect your dependencies, the problem may be more complex than I thought. But I guess it would not mind make some performance tests first. Commented Nov 6, 2014 at 19:49