System-versioned table schema modification failed because table '%1!s!' has %2!s! columns and table '%3!s!' has %4!s! columns.
System-versioned table schema modification failed because history table '%1!s!' is configured for change data capture. Consider ...
System-versioned table schema modification failed because history table '%1!s!' is not available or it is placed on a read-only ...
System-versioned table schema modification failed because online alter is not supported on system-versioned memory optimized ...
System-versioned table schema modification failed because system column '%1!s!' in history table '%2!s!' corresponds to a ...
System-versioned table schema modification failed because table '%1!s!' has %2!s! columns and table '%3!s!' has %4!s! columns. ...
System-versioned table SYSTEM_TIME period definition end column name not matching 'GENERATED ALWAYS AS ROW END' column name. ...
System-versioned table SYSTEM_TIME period definition start column name not matching 'GENERATED ALWAYS AS ROW START' column ...
Systematically create and register a data-tier application from an existing user database on a UCP enrolled instance of SQL ...
Table "%1!s!" does not have any records for configuration. This occurs when configuring from a SQL Server table that has ...