Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has table or column constraints defined. Consider dropping all table and column constraints and trying again.
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has custom unique keys defined. Consider dropping all ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has foreign keys defined. Consider dropping all foreign ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has IDENTITY column specification. Consider dropping ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has ROWGUID column specification. Consider dropping ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has table or column constraints defined. Consider dropping ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' has triggers defined. Consider dropping all triggers ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' is configured for change data capture. Consider dropping ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' is not available or it is placed on a read-only file ...
Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' is referenced by one or more BLOCK security predicates. ...