I'm surprised you're not find more posts. My 2 cents is to plan for this the same way you would if you used triggers. How often is parent table updated\deleted, ie. growth of history tbl? How long do you need the history for? How are you going to query the data & will you need extra indexes? etc.

Sounds very reasonable. The documentation recommends caution with blob datatypes + to implement a good indexing strategy if you create your own history table. ("strange" that it uses page compression when created automatically, but the docs recommends a cci?) learn.microsoft.com/en-us/sql/re...