Deprecation Announcement Event Class

 

The Deprecation Announcement event class occurs when you use a feature that will be removed from a future version of SQL Server, but will not be removed from the next major release. For greatest longevity of your applications, avoid using features that cause the Deprecation Announcement event class or the Deprecation Final Support event class.

Data column nameData typeDescriptionColumn IDFilterable
ApplicationNamenvarcharName 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.10Yes
ClientProcessIDintID 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.9Yes
DatabaseIDintID 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.3Yes
DatabaseNamenvarcharName of the database in which the user statement is running.35Yes
EventClassintType of event = 125.27No
EventSequenceintSequence of a given event within the request.51No
HostNamenvarcharName 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.8Yes
IntegerData2intEnd offset (in bytes) of the statement that is being executed.55Yes
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60Yes
LoginNamenvarcharName of the login of the user (either SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\username).11Yes
LoginSidimageSecurity 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.41Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7Yes
NTUserNamenvarcharWindows user name.6Yes
ObjectIDintID number of the deprecated feature.22Yes
ObjectNamenvarcharName of the deprecated feature.34Yes
OffsetintStarting offset of the statement within the stored procedure or batch.61Yes
RequestIDintID of the request containing the statement.49Yes
ServerNamenvarcharName of the instance of SQL Server being traced.26No
SessionLoginNamenvarcharLogin 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.64Yes
SPIDintID of the session on which the event occurred.12Yes
SqlHandleimageBinary handle that can be used to identify SQL batches or stored procedures.63Yes
StartTimedatetimeTime at which the event started, if available.14Yes
TextDatantextText value dependent on the event class captured in the trace.1Yes
TransactionIDbigintSystem-assigned ID of the transaction.4Yes
XactSequencebigintToken that describes the current transaction.50Yes

sp_trace_setevent (Transact-SQL)
Deprecation Final Support Event Class
Deprecated Database Engine Features in SQL Server 2014

Show: