AppDomain %1!s! was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical resource. %2!s!
Another user has modified the contents of this table or view; the database row you are modifying no longer exists in the ...
Answer query by getting data from one of the caches. This event may have a negative impact on performance when turned on. ...
AppDomain %1!s! (%2!s!) is marked for unload due to common language runtime (CLR) or security data definition language (DDL) ...
AppDomain %1!s! was unloaded by escalation policy to ensure the consistency of your application. Application failed to release ...
AppDomain %1!s! was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while ...
Applied schema changes and merged %1!d! data change(s) (%2!d! insert(s), %3!d! update(s), %4!d! delete(s), %5!d! conflict(s)) ...
Applied the snapshot and merged %1!d! data change(s) (%2!d! insert(s), %3!d! update(s), %4!d! delete(s), %5!d! conflict(s)) ...
Applying SET QUERY_GOVERNOR_COST_LIMIT or the query governor cost limit option of sp_configure may cause queries that ran ...
Applying transformation to access control entry '{1}' in order to apply it to directory '{0}' as part of the SQL Server Browser ...