Hi,
Yeah, I left a few things unsaid in my first post. Primarily, I suggested creating a tag path item exactly for the purpose of turning the status table into a look up table - the second part to that, which I should have mentioned, is that when snap-shotting the changes into the history table, you would only include the row index of the item, and not the path again.
You could definitely add an event id, though how you would wrap up all of the values into a particular event could be a bit tricky. The DB trigger that I first suggested probably wouldn’t work- it gets called for each row, not for the overall transaction (as far as I’m aware, could be wrong). A time based approach would work better (the snapshot query run every so often), but you would still have a difficult time ensuring that every record of the event was copied, and that no other records were included. Of course, if you actually have some sort of bit that indicates an “event” it becomes a lot easier and you can just trigger off that to run the copy query.
Let us know how it goes…