Temporal application time column '%1!s!' has invalid data type. Allowed data types are datetime2, smalldatetime, datetimeoffset, date and datetime.
TCM %1!s! has received an out of order message from brick id %2!s! and has to be stopped. Based on the state of the system ...
TCM manager has received a request for re-synchronization from brick id %1!s! and will now restart. Typical causes where ...
TDS reset connection protocol error. Client driver requested both ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact ...
TDSSNIClient failed to allocate memory while loading Extended Protection configuration settings. Check for memory-related ...
Temporal application time column '%1!s!' has invalid data type. Allowed data types are datetime2, smalldatetime, datetimeoffset, ...
Temporal FOR SYSTEM_TIME clause can only be set once per temporal table. '%1!s!' has more than one temporal FOR SYSTEM_TIME ...
Temporal table '%1!s!' already has history table defined. Consider dropping system_versioning first if you want to use different ...
Temporal tables require the lower boundary column name in SYSTEM_TIME PERIOD definition to match the GENERATED ALWAYS AS ...
Temporal tables require the upper boundary column name in SYSTEM_TIME PERIOD definition to match the GENERATED ALWAYS AS ...