Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' at ordinal %2!s! in history table '%3!s!' has a different name than the column '%4!s!' at the same ordinal in table '%5!s!'.
Setting a limit on the number of snapshots stored in history may result in the deletion of snapshots already created. Older ...
Setting ComVisible to false makes the types in this assembly not visible to COM components. If you need to access a type ...
Setting DirectQueryMode to any value other than Default is not supported when Analysis Services are not running in Tabular ...
Setting FILESTREAM ON failed on table '%1!s!' because it is not supported operation on system-versioned temporal tables. ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' at ordinal %2!s! in history table '%3!s!' has a different name ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same ANSI trimming semantics in tables '%2!s!' ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same CLR type in tables '%2!s!' and '%3!s!'. ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same collation in tables '%2!s!' and '%3!s!'. ...
Setting SYSTEM_VERSIONING to ON failed because column '%1!s!' does not have the same column set property in tables '%2!s!' ...