Collects information relevant to a warning or error returned by SQL Server.
Assembly: System.Data (in System.Data.dll)
Thetype exposes the following members.
|Class||Gets the severity level of the error returned from SQL Server.|
|LineNumber||Gets the line number within the Transact-SQL command batch or stored procedure that contains the error.|
|Message||Gets the text describing the error.|
|Number||Gets a number that identifies the type of error.|
|Procedure||Gets the name of the stored procedure or remote procedure call (RPC) that generated the error.|
|Server||Gets the name of the instance of SQL Server that generated the error.|
|Source||Gets the name of the provider that generated the error.|
|State||Some error messages can be raised at multiple points in the code for the Database Engine. For example, an 1105 error can be raised for several different conditions. Each specific condition that raises an error assigns a unique state code.|
|Equals(Object)||Determines whether the specified object is equal to the current object. (Inherited from Object.)|
|GetHashCode||Serves as the default hash function. (Inherited from Object.)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|ToString||Gets the complete text of the error message. (Overrides Object.ToString.)|
This class is created by the .NET Framework Data Provider for SQL Server when an error occurs. An instance of is created and managed by the SqlErrorCollection, which in turn is created by the SqlException class.
Messages with a severity level of 10 or less are informational and indicate problems caused by mistakes in information that a user has entered. Severity levels from 11 through 16 are generated by the user, and can be corrected by the user. Severity levels from 17 through 25 indicate software or hardware errors. When a level 17, 18, or 19 error occurs, you can continue working, although you might not be able to execute a particular statement.
The SqlConnection remains open when the severity level is 19 or less. When the severity level is 20 or greater, the server usually closes the SqlConnection. However, the user can reopen the connection and continue. In both cases, a SqlException is generated by the method executing the command.
The following example displays each within the SqlErrorCollection collection.
Public Sub ShowSqlException(ByVal connectionString As String) Dim queryString As String = "EXECUTE NonExistantStoredProcedure" Using connection As New SqlConnection(connectionString) Dim command As New SqlCommand(queryString, connection) Try command.Connection.Open() command.ExecuteNonQuery() Catch ex As SqlException DisplaySqlErrors(ex) End Try End Using End Sub Private Sub DisplaySqlErrors(ByVal exception As SqlException) Dim i As Integer For i = 0 To exception.Errors.Count - 1 Console.WriteLine("Index #" & i & ControlChars.NewLine & _ "Error: " & exception.Errors(i).ToString() & ControlChars.NewLine) Next i Console.ReadLine() End Sub
Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.