SQL Server Errors or Failures from Error: 8353 to Error: 8390

SQLServerF1

 

Error: 8353, Severity: 16, Event Tracing for Windows failed to start. %ls. To enable Event Tracing for Windows, restart SQL Server.
Error: 8354, Severity: 16, Event Tracing for Windows failed to send an event. Send failures with the same error code may not be reported in the future. Error ID: %d, Event class ID: %d, Cause: %ls.
Error: 8355, Severity: 16, Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdb failed to start. Event notifications in other databases could be affected as well. Bring msdb online, or enable Service Broker.

Error: 8356, Severity: 16, Event Tracing for Windows (ETW) failed to send event. The server has run out of memory. The same send failure may not be reported in the future.
Error: 8357, Severity: 16, Event Tracing for Windows (ETW) failed to send event. This may be due to low resource conditions. The same send failure may not be reported in the future.
Error: 8358, Severity: 16, Event Tracing for Windows (ETW) failed to send event. Event message size exceeds limit. The same send failure may not be reported in the future.
Error: 8359, Severity: 16, SQL Trace failed to send event notification. The server has run out of memory. The same send failure may not be reported in the future.
Error: 8360, Severity: 16, SQL Trace failed to send event notification. This may be due to low resource conditions. The same send failure may not be reported in the future.

Error: 8379, Severity: 10, Old style RAISERROR (Format: RAISERROR integer string) will be removed in the next version of SQL Server. Avoid using this in new development work, and plan to modify applications that currently use it to use new style RAISERROR.
Error: 8380, Severity: 10, SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) to connect to SQL Server using linked server ‘%.*ls’.
Error: 8381, Severity: 10, SQLOLEDB is no longer a supported provider. Please use SQL Native Client (SQLNCLI) for ad hoc connection to SQL Server.
Error: 8382, Severity: 10, Specifying table hints without using a WITH keyword is a deprecated feature and will be removed in a future version.
Error: 8383, Severity: 10, Specifying HOLDLOCK as a table hint without parentheses is a deprecated feature and will be removed in the next version of SQL Server.
Error: 8384, Severity: 10, Use of space as a separator for table hints is a deprecated feature and will be removed in a future version. Use a comma to separate individual table hints.
Error: 8385, Severity: 10, The select list of an aggregate indexed view must contain count_big(*) in 90 compatibility mode and higher.
Error: 8386, Severity: 10, Use of hint “%.*ls” on the target table of INSERT is deprecated because it may be removed in a future version of SQL Server. Modify the INSERT statement to remove the use of this hint.
Error: 8387, Severity: 10, The indirect application of table hints to an invocation of a multi-statement table-valued function (TVF) through a view will be removed in a future version of SQL Server. Remove hints on references to view “%.*ls” because it references a multi-statement
Error: 8388, Severity: 10, The ability to return results from triggers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.
Error: 8389, Severity: 10, The ALL permission will be removed in a future version of SQL Server. Avoid using this permission in new development work and plan to modify applications that currently use it.
Error: 8390, Severity: 10, The ‘::’ function calling syntax will be removed in a future version of SQL Server. Replace it with “sys.”.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *