Dear devs,

I am reaching out to you, because I wanted to discuss a feature request for the history of system versioned temporal tables.

Is it possible to add a special setting so that I can update and delete the history?

Update, e.g. because sometimes it is necessary to pseudo-/anonymize former customer data. 

Delete, e.g. because former customers demand all data must be deleted.

German dsgvo rules...

I know it opposes the idea of having a non changeable history.

But I think there are cases where it is justified and needed.

So I am asking for something like

system_versioning_delete_history

system_versioning_update_history

Or does there exist some other workaround to do this?

Other ideas:

- add a where clause to "delete history"

- add update history with where clause

- drop system versioning, do the update/ delete and enable system versioning again in one commit?

Why must the history be dropped when I disable it for a table again? Could it be kept?

By the way the "simple" drop of system versioning didn't work. Needed to drop ts, te cols, period and the system versioning in one alter.

Another question: How to migrate system versioned tables with SQL?

Thank you!

Kind regards

Robert