Create mock data based on system versioned table

Hi @BramG,

Awesome idea!, we currently are using the following workaround for the time being:

First off disabling the system versioning on the table, then inserting the necessary data into the history table, then re-enabling the system versioning.

Code we used as example:

declare @sql nvarchar(max) = ''

set @sql = 'alter table [table] set ( system_versioning = off ); '
exec sp_executesql @sql

set @sql = 'insert into [table]_history ([cols], tsf_valid_from, tsf_valid_to) values ([COL_VALUES], [tsf_valid_from], [tsf_valid_to]);'
exec sp_executesql @sql

set @sql = 'alter table [table] set ( system_versioning = on ( HISTORY_TABLE = dbo.[[table]_history], DATA_CONSISTENCY_CHECK = ON));'
exec sp_executesql @sql; 

For the idea, we'll need to find a good way of integrating this in the data model so we can more easily make this happen. Let's gather some votes 

Hi! The last release event implied that this will be in 2023.2 release. Is that correct?

Hi @Mark Jongeling ! I have too many tables that are system versioned and enough data to insert into .There is another solution to use the mock data with the system versioned tables?

Not sure if we mentioned that, but we did add the ability to have mock data for Views. This idea remains open.

From 2023.2, you have the option to write a Mock data preparation query in which you can add data to the system-version tables. Sadly this is not that trivial yet so my example is still the only way for now.

History tables are not part of the Data model so it requires a bit more effort to implement. However, it's not impossible but we have not yet planned the implementation of this idea.