Possible data truncation on output parameter, "%1!d!". The task cannot determine the datetime type of the output parameter ...

Possible data truncation on output parameter, "%1!d!". The task cannot determine the datetime type of the output parameter because the BypassPrepare property is set to True. If the output parameter type is datetime2, use a string variable instead of a datetime variable for the output parameter to prevent truncation. To allow the task to determine the output parameter type in the future, set BypassPrepare to False.

Point-in-time recovery is not possible unless the primary filegroup is part of the restore sequence. Omit the point-in-time ... Policy '{0}' has been violated by '{1}'. This transaction will be rolled back. Policy condition: '{2}' Policy description: ... Polish, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ... Polish, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ... Possible data truncation on output parameter, "%1!d!". The task cannot determine the datetime type of the output parameter ... Possible data truncation on parameter, "%1!d!". To prevent truncation, use a string variable instead of a datetime variable ... Possible inconsistent state in the distribution database: dist_backup_lsn {%1!s!:%2!s!:%3!s!}, dist_last_lsn {%4!s!:%5!s!:%6!s!}. ... Post-online processing for availability group '%1!s!' has been terminated. Either post-online processing has already completed, ... Potential data loss may occur due to inserting data from input column "%1!s!" with data type "%2!s!" to external column "%3!s!" ...