Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' in history table '%2!s!' corresponds to a generated always column in table '%3!s!' and cannot be nullable.
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same sparse storage attribute in tables '%2!s!' ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same XML Schema Collection in tables '%2!s!' ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not use identical encryption in tables '%2!s!' and '%3!s!'. ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' has data type %2!s! in history table '%3!s!' which is different ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' in history table '%2!s!' corresponds to a generated always ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' contains invalid records with end of period set before ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' contains invalid records with end of period set to a ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has computed column specification. Consider dropping ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has custom unique keys defined. Consider dropping all ...