OLEDB Errors Event Class
The OLEDB Errors event class occurs in Microsoft SQL Server when a call to an OLE DB provider returns an error. Include this event class in traces to view a failed HRESULT from an OLE DB provider.
When the OLEDB Errors event class is included in a trace, the amount of overhead depends on how frequently OLE DB provider errors occur against the database during the trace. If such errors occur frequently, the trace might significantly impede performance.
OLEDB Errors Event Class Data Columns
Data column name |
Data type |
Description |
Column ID |
Filterable |
|---|---|---|---|---|
ApplicationName |
nvarchar |
Name of the client application that created the connection to an instance of SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program. |
10 |
Yes |
ClientProcessID |
int |
ID assigned by the host computer to the process where the client application is running. This data column is populated if the client provides the client process ID. |
9 |
Yes |
DatabaseID |
int |
ID of the database specified by the USE database statement or the default database if no USE database statement has been issued for a given instance. SQL Server Profiler displays the name of the database if the ServerName data column is captured in the trace and the server is available. Determine the value for a database by using the DB_ID function. |
3 |
Yes |
DatabaseName |
nvarchar |
Name of the database in which the user statement is running. |
35 |
Yes |
Error |
int |
The HRESULT returned by the provider. |
31 |
Yes |
EventClass |
int |
Type of event = 61. |
27 |
No |
EventSequence |
int |
Sequence of OLE DB event class in batch. |
51 |
No |
GroupID |
int |
ID of the workload group where the SQL Trace event fires. |
66 |
Yes |
HostName |
nvarchar |
Name of the computer on which the client is running. This data column is populated if the client provides the host name. To determine the host name, use the HOST_NAME function. |
8 |
Yes |
IsSystem |
int |
Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user. |
60 |
Yes |
LinkedServerName |
nvarchar |
Name of the linked server. |
45 |
Yes |
LoginName |
nvarchar |
Name of the login of the user (either SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\Username). |
11 |
Yes |
LoginSid |
image |
Security identification number (SID) of the logged-in user. You can find this information in the sys.server_principals catalog view. Each SID is unique for each login in the server. |
41 |
Yes |
MethodName |
nvarchar |
Name of the OLE DB method. |
47 |
Yes |
NTDomainName |
nvarchar |
Windows domain to which the user belongs. |
7 |
Yes |
NTUserName |
nvarchar |
Windows user name. |
6 |
Yes |
ProviderName |
nvarchar |
Name of the OLE DB provider. |
46 |
Yes |
RequestID |
int |
ID of the request containing the statement. |
49 |
Yes |
SessionLoginName |
nvarchar |
Login name of the user who originated the session. For example, if you connect to SQL Server using Login1 and execute a statement as Login2, SessionLoginName shows Login1 and LoginName shows Login2. This column displays both SQL Server and Windows logins. |
64 |
Yes |
SPID |
int |
ID of the session on which the event occurred. |
12 |
Yes |
StartTime |
datetime |
Time at which the event started, if available. |
14 |
Yes |
TextData |
nvarchar |
Parameters sent and received in the OLE DB call. |
1 |
No |
TransactionID |
bigint |
System-assigned ID of the transaction. |
4 |
Yes |
Zobacz także
Odwołanie
sp_trace_setevent (Transact-SQL)