Applying SET QUERY_GOVERNOR_COST_LIMIT or the query governor cost limit option of sp_configure may cause queries that ran in an earlier version of SQL Server not to run in SQL Server 2005 or later versions because of changes in query cost modeling. Update the setting to an appropriate value or set it to 0 to specify no limit.
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 ...
Applying transformation to access control entry '{1}' in order to apply it to registry key '{0}' as part of the SQL Server ...
Applying transformation to directory path '{0}' in order to add an access control entry as part of the SQL Server Browser ...
Applying transformation to registry key path '{0}' in order to add an access control entry as part of the SQL Server Browser ...