Setting SYSTEM_VERSIONING to ON failed because history table '%1!s!' is referenced by one or more BLOCK security predicates. Consider removing the BLOCK security predicates referencing this table and trying again.
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. ...
Setting SYSTEM_VERSIONING to ON failed because system column '%1!s!' in history table '%2!s!' corresponds to a period column ...
Setting SYSTEM_VERSIONING to ON failed because table '%1!s!' contains invalid records with end of period set before start. ...
Setting the cost limit to a small value may inhibit applications such as Microsoft SQL Server Management Studio from functioning ...
Setting the persisted property of the selected column to false will delete relationships with the following tables: . Do ...