MZ@ !L!This program cannot be run in DOS mode. $Uu]333c3c3Rich3PEd 5O"  |Xf@{~X<.rsrc{|@@ V(@Xp     0H`x 8Ph !"#($@%X&p'()*+,-.0/H0`1x2345678 98:P;h<=>?@AB C( D@ EX Fp G H I J K L M N0 OH P` Qx R S T U V     0  @  P  `  p                        0  @  P  `  p                        0  @  P  `  p                      0 @ P ` p             0 @ P ` p             0 @ P ` p  |#6' +R(/ 43@t69?@GKl`R@ ^pctkquZ4| ąN8 L (ĨH4J 4(\ :  H"d0,dxx"J&+\/*$7=LEMV0 @_rdz0j,\oq }"<LJV  , 8 r 4 Pd(^   p  ( d5HD O Z 4d qy.4Ć~DZGlobally Unique IDEvent schema version ETW Channel(Extended events for Microsoft SQL ServerEvent grouping keywords File I/O modeTrace flag type Event pair*Reason page compression attempt has failed"Change Tracking Cleanup Status Ids!Sort subsystem tracing sub-eventsReason why log was flushedType of log block allocation-Degree of Parallelism (DOP) calculation stageRead or write operationLocation of pageSort warning typesShutdown state of a queryDatabase file types0The transaction isolation used by a transaction.Transaction stateTransaction type9The stage in the build operation that generated the event The cause of the lock escalationHash warning types$The type of statement being executedQuery plan typeSend/receive pair?HADR Windows Server Failover Clustering change notifier status.gHADR mutex acquisition state, for tracing important points during acquisition/release of mutex objects.PAoHADR AR critical section entry state, for tracing important points during entering/exiting of critical section.Alter Database Set option type*Result of the OIB with LOB cleanup process\Generic binary enum can be used to indicate that an event is either of send or receive type.*Indicates full or partial session context.AlwaysOn DDL operationAlwaysOn DDL operation phase Lock resourceLock owner type Lock mode Latch mode Latch classFastLoadContext StateLog operation type Lock result%Query processor logical operator type&Query processor physical operator typeQuery iterator tree node type Page classQuery execution warning typesBitmap runtime trace levelPage error typesContext for log operationsLog shipping notifications Object typeCurrent phase of DBCC CHECK*$Request type for an incoming message"Reply type for an incoming messagePage Allocator typesPage Split Operation StateSend/Recv/Drop(Reason for dropping a particular messagePA Message TypeHADR Session StateHADR Configuration State Reason for change replica statusFlow Control ActionHADR DBR scan State\Windows Server Failover Clustering resource state. Used as HADR Availability replica state.=Windows Server Failover Clustering node state. Used by HADR.$AlwaysOn Availability Replica State.,AlwaysOn Availability Replica Manager state.HADR DBManager StateHADR DBManager Object TypeHADR DBManager rolesHADR DBManager Shutdown typeHADR DBManager Function TraceHADR DBManager EnabledHADR DBManager suspend statusHADR DBManager suspend sourceHADR DBManager Undo PhaseHADR task typesHADR task statesHADR Commit PolicyHADR Sync State HADR file metadata request typesHADR FileStream Open ModeHADR FileStream Transfer TypeHADR dbmgr test pointsHADR undomgr test points$HADR backup on secondary test pointsHoBt Schema Mgr operationHoBt Schema Mgr DDL operationHoBt Schema Mgr Allocation unit$HoBt Schema Mgr HoBt allocation page&HoBt Schema Mgr HoBt compression levelHoBt Schema Mgr HoBt LOB status!HADR auto page repair test pointsResource notificationLog consumer activityremote RPC request typeremote RPC LOB actionClassIdEnum mappingDatabase stateDatabase DDL agent request type%Phase of the Create-Replica protocol.Database Reference Type.DB Lock options.#Source of the lock request for GLM.!Locking policy requested for GLM.PAOThe file modification type in a ALTER DB ... MODIFY FILE database DDL statementFile group type7File group property used in ALTER DB...MODIFY FILEGROUP Buffer statusResource owner typeMemory Steal from options"OLE DB range options for SetRange.File read completeddWhen set to 1, collect_path enables collection of path. By default the path column is not generated.}The binary representaion of the data that was read from the file. This data is used for troubleshooting by Microsoft support.mWhen set to 1, collect_io_data enables collection of io_data. By default the io_data column is not generated.Associated KeywordNumber of bytes readFile write completedNumber of bytes writtenBuffer manager database pagesPA3Buffer manager page life expectancy in millisecondsBuffer manager target pagesBuffer node database pages0Buffer node page life expectancy in millisecondsBAmount of memory the server is currently using for database cache.3Amount of memory the server is currently not using.Amount of memory the server has reserved for future usage. This value shows current unused amount of the initial grant shown in Granted Workspace Memory (KB).^Amount of memory the server is currently using for the purposes other than the database pages.&Ideal amount of memory for the server.0Total amount of memory the server has committed.EAmount of memory the server is using on this node for database pages.6 Amount of memory the server is not using on this node,Non NUMA-local amount of memory on this node]Amount of memory the server is using on this node for the purposes other than database pages.$Ideal amount of memory for this node=Total amount of memory the server has committed on this node."Catalog metadata cache entry added$Catalog metadata cache entry removed#Catalog metadata cache entry pinned%Catalog metadata cache entry unpinnedCatalog metadata cache hit#Databases backup/restore throughput?Fired at locations where it's useful for test to inject a delay1Uniquely identifies the location for a test delay/Databases bulk insert rows (due to BULK INSERT);Databases bulk insert throughput in KB (due to BULK INSERT)Databases DBCC logical scanDatabases log cache hitDatabases log cache readDatabases log file size changed$Databases log file used size changedDatabases log truncation(Databases log flush wait in millisecondsDatabases log flushDatabases log growthDatabases log shrinkDatabases shrink data movementLocks lock waits User settable(Latch acquired (available in debug only)wPage id is obtained during calls to latch acquire which may be at a time when page id is either stale or uninitialized.(Latch released (available in debug only) Ghost cleanup Lock acquiredOccurs when a lock is acquired on an object. Use this event to troubleshoot data contention issues that are caused by locks that are being held for long periods of time.?The ID of the locked object, when lock_resource_type is OBJECT.UThe ID of the lock partition, when lock_resource_type is OBJECT, and resource_1 is 0.jThe ID of the locked object, when lock_resource_type is OBJECT. For other lock resource types it will be 0?The ID of the object that requested the lock that was acquired.XThe time (in microseconds) between when the lock was requested and when it was canceled.The description of the lock resource. The description depends on the type of lock. This is the same value as the resource_description column in the sys.dm_tran_locks view.When set to 1, collect_resource_description enables collection of resource_description. By default the resource_description column is not generated.When set to 1, collect_database_name enables collection of database_name. By default the database_name column is not generated.Occurs when a lock on an object has been released. Use this troubleshoot data contention issues that are caused by locks being held for long periods of time,Occurs when a lock is released on an object.kThe ID of the locked object, when lock_resource_type is OBJECT. For other lock resource types it will be 0.?The ID of the object that requested the lock that was released.A description of the lock resource. The description of the lock resource depends on the type of lock. This is the same value as the resource_description column in the sys.dm_tran_locks view.DeadlockROccurs when an attempt to acquire a lock is canceled for the victim of a deadlock.-The ID of the object that requested the lock.bThe time (in microseconds) between when the lock was requested and when the deadlock was resolved.AOccurs when the redo thread blocks when trying to acquire a lock.aThe time (in microseconds) when the lock was requested and when it was granted. Will always be 0. Page splitSplit OperationPhysical page readPhysical page writeLatch suspend beginrOccurs when a the executing task must suspend while waiting for a latch to become available in the requested mode.*The memory address where the latch residesThe mode of the latch requestThe latch type;The number of requests to keep the latched object in memory(The number of shared owners on the latch*The number of updating owners on the latch+The number of exclusive owners on the latch4The number of requests to destroy the latched object,Indicates if there are waiters for the latch'Indicates if the latch is a super latchPA:Indicates if the latch is poisoned and should be destroyedaThe amount of time the requesting task will wait for the latch to become available before failingTThe database id of the page the latch protects, 0 if the latch is a not a page latchPThe file id of the page the latch protects, 0 if the latch is a not a page latchPThe page id of the page the latch protects, 0 if the latch is a not a page latchLatch suspend endDOccurs when the executing task is resumed after waiting for a latch.@Indicates if the latch wait resulted in acquisition of the latchLThe amount of time (in microseconds) that the requestor waited for the latchYOccurs when there is a timeout waiting for a latch possibly causing performance problems.XTask address owning the latch when it is acquired in update, exclusive, or destroy modesIIndicates if the task will continue to wait for latch to become availableLatch promotion1Occurs when a latch is promoted to a super latch.Latch demotion:Occurs when a super latch is demoted to an ordinary latch.FlushFileBuffers called File readNumber of bytes to be read File writtenNumber of bytes to be writtenCheckpoint has begunCheckpoint has ended0File writes issued to sparse file for replica DB2Target for outstanding data pages has been changed6Found we were over target and queued background writesHBackground writes queued to allow truncation of simple recovery databaseWBackground writes queued to allow truncation dirty page point to get to last checkpoint=Chose not to enqueue a checkpoint as we are within the targetMBackground writes forced to allow oldest dirty page to get to last checkpointMChose to enqueue an incremental checkpoint as we are near our recovery targetAllocation ring buffer recordedvWhen set to 1, collect_call_stack enables collection of call_stack. By default the call_stack column is not generated.1A page that should have been constant has changedDatabase attachedDatabase detachedDatabase startedDatabase stoppedTrace flag changedChange Tracking Cleanup%Tracks SYS.SYSCOMMITTAB Table Cleanup'Deadlock monitor performance statistics(Start ticks of the most recent LDM cycle5Duration of the most recent LDM cycle in milliseconds*Average LDM cycle duration in milliseconds&Max LDM cycle duration in milliseconds.Deadlock monitor memory utilization statistics!Deadlock Monitor state transitionCDeadlock monitor PMO status at various checkpoints in the LDM cycle9Deadlock monitor local wait-for graph dump in binary form-An attempt to compress a database page failed7Entry and exit tracking for page compression operationsLong IO detected!Various statistics about the sort1Sort adding merge runs to the merge run directory&Sort internal events and state changes6Sort adjusting the memory grant of an in-progress sort)Produces a deadlock report in XML format.5An XML document describing the results of a deadlock.&Index leaf page disfavored during scan;Prefetch issued for a whole extent instead of a single page6Occurs when fastloadcontext is activated / deactivatedDOccurs when a text info record is read by the replication logreader.FOccurs when a text pointer is being read by the replication logreader.PAJOccurs when a filestream info record is read by the replication logreader.aOccurs when the replication logreader encounters a partial rollback for a particular transaction.@Occurs when the replication logreader agent reads an EOR record.bOutputs transactions which are added to the repl hash table as well as some hash table statistics.QOccurs when the replication logreader agent executes a horizontal filtering proc.CDC Logscan session Information+session ID is recycled after server restart/number of seconds between StartTime and EndTimeOnumber of errors encountered during this session, accumulated across all phasesnnumber of (replicated or tracked) transactions processed, available in phase 2, after which it keeps unchanged[number of log records scanned through, available in phase 2, after which it keeps unchangednumber of DDL operations detected, for changes to RE schema, SE schema and article schema, available in phase 6, after which it keeps unchangedRnumber of commands processed, available in phase 7, after which it keeps unchangedDdatediff (in sec) between end time and commit time of last committed;number of consecutive empty scans, beginning from this scan)1 indicates failed, 0 indicates otherwiselogscan start time&logscan end time, available at phase 8odatetime, commit time of last any commit lsn processed, available after the end of phase 2, then kept unchangedJcommit time of last CDC tracked commit lsn processed, available in phase 7current scan started from this LSN, available after at beginning of phase 2, DMV users should call PackLSN(...) before display#current LSN, available from phase 2Gend of log while current scan ended, available after the end of phase 2bbinary(10), last any commit LSN processed, available after the end of phase 2, then kept unchangedAearliest CDC tracked begin LSN in this scan, available in phase 7;last CDC tracked commit LSN processed, available in phase 7CDC Error InformationFDatabase recovery at the beginning of user transaction rollback stage.8Database recovery at the end of physical recovery stage.PFile manager delete or mark file entries from master database and this database.3A new and unused database Id is found and reserved.IA database recovery unit metadata is inserted in masterDB on local brick.PAbBegin the request to create a database segment at some remote or local brick from the local brick.SThe request to create a database segment at some remote or local brick is finished.Xuser data is dropped, and logical metadata are truncated in one matrix database segment.DOccurs when the file manager started to modify a database file name.BOccurs when the file manager starts validating a file declaration.possibly invalid value)Failure encountered in recreating a file.PThe files of a database segment are remapped with sys.master_files system table.}The recovery unit files metadata, sys.database_files, of a database segment is copied from the sys.master_files system table.SFile manager created information for a physical file group information in metadata.DOccurs when all the files for a database segment have been attached.%One database segment begins starting.jThe data structure DBTable is initialized according to registered information in Master database catalogs.CThe startup process of DBTable data structure is done successfully.-The Database is migrated to MatrixDB segment.WThe database is opened at one brick successfully and a shared lock is held by the user.Uthe new database segment id is updated at the boot block and clone tables for matrix.HThe state of a database segment is changed in the local database segment*Matrix Database aggregate state is changedPOne database segment sent a state change message to the primary database segmentQThe primary database segment received the state of the secondary database segmentxDatabase DDL or operation agent starts to execute the local operation upon receiving a valid request from a remote brickRMetadata Id of the targeted database, or 0 if the id is not available at the time.XLogical name of the targeted database, or NULL if the name is not available at the time.ZDatabase DDL or operation agent finishes the local operation requested from a remote brickYDatabase DDL or operation agent sends a request to a remote brick to execute an operation5A database DDL or operation agent request is finishedSAll database segments are dropped, and the physical files may or may not be deletedDDatabase is renamed, but the transaction has not been submitted yet.GOne or more database option changes are changed in metadata or bootpageMDatabase bootpage is sync'ed with the DB Registration information in metadataADBTABLE structure is refreshed after database options are changed`Occurs when all database files has already been formatted on disk for an ADD FILE DDL statement.POccurs when the file manager added file metadata in the master database segment.?Occurs when a database file is added into the database segment.+Occurs when add file action is rolled back./Occurs when the file is prepared to be dropped.*Occurs when drop file action is committed.,Occurs when drop file action is rolled back.FOccurs when the file manager modified the property of a database file.QOccurs when the database agent on the connect brick starts to create a filegroup.OOccurs when the database agent on the connect brick starts to drop a filegroup.;Occurs when the database MetaData version has been updated.MOccurs when the file group manager changed the name for a physical filegroup.QOccurs when the file group manager changed the property for a physical filegroup.*Number of group commit waiters has changedLog flush was requestedLog write buffer was allocatedPALog block was freed0After some amount of log is snipped but not all.6DBCC CHECK* tracing: entering a new phase of the checkCTraces the number of messages a CHECK* thread has sent or received.YTraces the number of logical, physical, and read-ahead IOs a CHECK* thread has performed.%Traces page latch and IO latch waits./Traces a message request sent to a remote brick-Traces a message reply sent to a remote brick4Traces Checkpoint DB message sent to a remote brick.,Reports the DBID used for Transient Replica.5Traces Create Replica message sent to a remote brick.3Traces recover-to age response from a remote brick.^Occurs when all messages are sent and the replica is about to be created on the connect brick.!Signals completion of local call.#Signals the end of the conversation2Signals the begining of drop replica db operation.%Matrix Backup/Restore protocol events_Indicates the id that the coordinator uses to identify the worker that this messages relates toHIndicates if firing this event relates to sending or receiving a messageGIndicates if this was fired before or after sending/receiving a messageTIndicates if the message is a request (from coordinator) or a response (from worker)Class type id of messageSFired before matrix restore redo begins when target restore AGE is being determinedCurrent restore target AGEBMatrix Backup/Restore Leading Meta Data read of Backup Config Type5Archive metadata field offset within the archive fileArchive metadata field sizeArchive metadata field value Archive metadata field name)File name of the archive being processed BMatrix Backup/Restore Leading Meta Data read of Backup Group CountDMatrix Backup/Restore Leading Meta Data read of Group BackupSet GuidPAHMatrix Backup/Restore Leading Meta Data read of Primary File Group FlagsCMatrix Backup/Restore Trailing Meta Data read of Common Restore AGEOOccurs when an in-doubt transaction is resolved during matrix restore recovery.The local transaction ID.DThe node transaction ID that higher level components can understand.rThe local node transaction ID. This is used to differentiate between either transaction ID or resource manager ID.The transaction outcome. This will be true if the resolution was to commit the transaction or false if the resolution was to rollback the transaction.^The AGE associated with the transaction outcome. This is 0 if the transaction was rolled back.Occurs when matrix restore recovery has completed. It may not occur if there are no in-doubt transactions with commit outcomes to be processed during matrix restore recovery.AThe number of in-doubt transactions that were resolved as commit.CThe number of in-doubt transactions that were resolved as rollback.&Metadata create local temporary object&Metadata delete local temporary object'Metadata create global temporary object'Metadata delete global temporary object,Query Driver received the activation messagePAHQuery Driver received the activation message but not fully populated yet+Query Driver sending the activation message(Query Driver sent the activation message0Query Driver sent the statistics profile message4Query Driver received the statistics profile message+Query Driver sent the rows affected message/Query Driver received the rows affected message Query compilation is initializedQuery tree is compiledQuery compilation is prepared.Degree of Parallelism (DOP) calculation begins'Degree of Parallelism (DOP) calculation Runtime query iterator is cachedRuntime query iterator is uncached. This indicates that a previously cached version of the query runtime is being used. This can be correlated with the query_scan_cache event'Runtime remote query instance is cachedRuntime remote query instance is uncached. This indicates that a previously cached version of the query instance runtime is being used. This can be correlated with the query_instance_cache_remote_insert eventQuery memory pre-grantQuery memory post-grantQuery memory return grant?Query memory request calculation for memory consuming iterators%Query attempt to request memory grant Query reserve buffer pool memoryRuntime query is shutdownRuntime query is setupQuery topology5Occurs when a query driver is removed from the cache.Connect brick id. Query id.Bitmap data is finalized%Hash iterator's runtime actual memory#Parallel producer thread is startedNUsed for nested loop join, occurs after producer receive correlated parametersKUsed for nested loop join, occurs after consumer send correlated parametersCOccurs after a SQL statement is compiled. This event returns an XML representation of the estimated query plan that is generated when the query is compiled. Using this event can have a significant performance overhead so it should only be used when troubleshooting or monitoring specific problems for brief periods of time.FThe ID of the database for the object that the plan is associated with8The type of the object that the plan is associated with.6The id of the object that the plan is associated with.3The estimated number of rows returned by the query.2The estimated execution cost of running the query.HThe amount of time (in microseconds) which took to compile the statement_Indicates the amount of CPU time (in microseconds) consumed during compilation of the statementThe number of times the statement has been recompiled. This is only available when compiled_object_type is Query from Stored Procedure or BatchPThe beginning offset into the query text of the statement that is being removed.MThe ending offset into the query text of the statement that is being removed.gThe handle that can be used to obtain the plan XML from the dm_exec_query_plan dynamic management view.gThe handle that can be used to obtain the query text from the dm_exec_sql_text dynamic management view.8The name of the object that the plan is associated with.3The XML representation of the optimized query plan.PAIThe name of the database for the object that the plan is associated with.DOccurs after a SQL statement is compiled. This event returns an XML representation of the estimated query plan that is generated when the query is optimized. Using this event can have a significant performance overhead so it should only be used when troubleshooting or monitoring specific problems for brief periods of time.Occurs after a SQL statement is executed. This event returns an XML representation of the actual query plan. Using this event can have a significant performance overhead so it should only be used when troubleshooting or monitoring specific problems for brief periods of time.GIndicates the CPU time (in microseconds) that is consumed by the query.GThe amount of time (in microseconds) that it took to execute the query.-Query execution trace (internal testing only)jOccurs before allowing memory consuming remote exchange operator to be executed on other bricks in Matrix.Occurs on classifying current memory consuming remote exchange operator consumes relative small amount of memory, then will allow executing immediately without asking resource permission.SOccurs after all memory consuming remote exchange operators are executed in Matrix. RX about to allocate row buffersRX allocates row buffersRX releases row buffersRX about to send row buffersRX sends row buffersRX receives row buffers$RX about to send an activate messagePARX sends an activation messageQuery is starting upCreating RPC column accessor.Accessor pointer.Number of column bindings./Total buffer size for column bindings in bytes.Releasing RPC column accessor.Closing RPC rowset.Waking up RPC rowset.-Whether fragment enumerator is in clone loop.$Whether RPC is using a local rowset.$Setting RPC rowset to dormant state.Setting range for RPC rowset.Bitmask of range options."Fetching next row from RPC rowset.Getting data from RPC rowset.PA-whether this is the new value after an updateSetting data in RPC rowset.Inserting row in RPC rowset.Deleting rows from RPC rowset.$Whether the row was already deleted.*Fetching row by key value from RPC rowset.Key accessor pointer.+Number of column bindings for key accessor.5Key accessor's total buffer size for column bindings.Data accessor pointer.,Number of column bindings for data accessor.6Data accessor's total buffer size for column bindings./Whether the RPC rowset needs to cache the keys."Inserting index row in RPC rowset.Ending update in RPC rowset."Setting cardinality in RPC rowset."Preparing to delete in RPC rowset.(Locating and deleting row in RPC rowset.(Locating and updating row in RPC rowset.(Locating or inserting row in RPC rowset."Switching partition in RPC rowset. Processing SetRange RPC command.Processing GetData RPC command.!Processing FetchData RPC command.Processing SetData RPC command. Row pointer.!Processing InsertRow RPC command.!Processing DeleteRow RPC command.'Processing PrepareToDelete RPC command.!Processing SetMarker RPC command."Processing GotoMarker RPC command.!Processing LobAction RPC command.Preparing WakeUp RPC command. Table name. Index name. Schema name. Preparing FetchData RPC command.Preparing GetData RPC command.Preparing SetRange RPC command."Whether the range is over one row.0Preparing SetRange RPC command with cached keys.Preparing SetData RPC command. Preparing InsertRow RPC command."Whether to use LocateOrInsert API.&Preparing PrepareToDelete RPC command. Preparing DeleteRow RPC command. Preparing SetMarker RPC command.!Preparing GotoMarker RPC command.PAXOccurs when each batch processing operator get a new batch of data from child operators.4Occurs when hash table is built in batch processing.0Occurs when bitmap is built in batch processing.?Occurs when range elimination map is built in batch processing.<RPC runtime collection cache hit, with cache key in request.Type of RPC request.Request db id.Request table id.Request index id.6Hash value of the lookup key for a rowset cache entry.*Cache entry identifier in the cache store.`Used for faster lookup and to avoid sending and comparing the full key for a rowset cache entry.JRPC runtime collection cache hit, using request type instead of cache key."RPC runtime collection cache miss.,Inserting RPC runtime collection into cache.+Removing RPC runtime collection from cache.&Flushing RPC runtime collection cache. Creating RPC runtime collection.Initializing RPC runtime.Waking up RPC runtime.RPC runtime cache hit.RPC runtime cache miss.!Inserting RPC runtime into cache.BTrue when an entry has been successfully insterted into the cache. Removing RPC runtime from cache.The hash_value field can be used to track RPC cache behavior by relating it to the hash_value field in other cache related events such as rpc_cache_insert.Creating RPC runtime.Sending RPC request.Destination brick id.&Hash value for the rowset cache entry.Use RPC cache.Receiving RPC request.Source brick id. Preparing LobAction RPC command.Type of RPC LOB action. Column Id.Offset into LOB.Length of data.Size of data in bytes.Executing RPC lob action.)No CQSCAN cache due to memory limitation.Cache ThreasholdSize of requested memory@Occurs when column store scan get one batch in batch processing.HOccurs when column store scan does switch partition in batch processing.0Occurs when partition elimination info is built./Remote DMV stream client side open call is made*Remote DMV stream is open call is servicedPA2Remote DMV stream get_row client side call is made*Remote DMV stream get_row call is serviced0Remote DMV stream release resources call is made4Remote DMV stream release resources call is serviced#Remote DMV stream cache entry addedRemote DMV stream cache hitRemote DMV stream cache miss-Remote DMV stream blob fetch call is serviced?Client call is made to fetch blob data from a remote DMV streamMetadata cache entry hitMetadata cache entry miss3Event which fires when we're acquiring new messagesFUse this event to trace HADR transport messages throughout the system.AIndicates whether the message is being sent, received or dropped.6Indicates the reason that the message is being logged.#The sequence number of the message.]The last sequence number from the target Availability Replica which we have received locally.The type of the message.DThe unique ID associated this this particular message logging event.FThe ID of the Availability Group with which the message is associated.SThe ID of the local Availability Replica which is sending or receiving the message.*The ID of the remote Availability Replica.EThe ID of the transport session which the message is associated with.The ID of the database replica.9Use this event to help trace HADR configuration messages.;Event which fires when we're processing an incoming message?This event occurs when a HADR transport session changes states.Indicates session state changeshOccurs when the ucs connection id associated with the hadron transport replica is registered or changes.JIndicates that a flow control action has occured for a particular replica.NIndicates that a flow control action has occured for a particular dbr/replica.#Indicates db_manager state changes.PACurrent DbMgr state.Proposed DbMgr state.Target DbMgr state.Hadron DbMgr object type.Hadron Availability Group Id.Hadron Availability Replica Id. Hadron Availability Database Id.Indicates db_manager api calls.Instance Database id.Function entry or exit flag.Api function name.LSN Sync message.Message Id from Header log.Last block flushed.Current end of log. Redo LSN.Local truncation point.Hadr truncation point.Secondary recovery blockid.)Common harden block for sync secondaries."Minimum filestream recovery point.#Hardened filestream recovery point.Establish DB message.Source of message.Log backup lsn.-Minimum filestream LSN skipped by log backup. Redo blockid.Last time seen by redo.DBReplicaStatusChange message.Reason enum for status change.Redo processing on secondary. Database id.Undo processing on secondary.Llast block flushed.'Recovery blockid = target for log snip. Current blockid of undo scanner.-Last log block required to secure undo pages.Page id requested by undo.Phase of the undo. Queue restart hadron datadabase.Clean shutdown flag.Log accept flag.Start hadron database.Shutdown hadron datadabase.4Change user status for a hadron controlled database.Users allowed flag.Kill current users (immediate).8Change log scan status for a hadron controlled database. Redo active.Immediate stop flag.StopAt point for scan.>Change suspend/resume status for a hadron controlled database.Suspend Resume flag. Source of suspend resume action.Restart hadron database."HADRON worker pool thread actions. Thread Id.SOS_Result of the action.Action taken on the thread. HADRON worker pool task actions.Pointer/Id of the task.+Wait time before task should get scheduled.Type of the task.State of the worker task./HADRON thread pool worker thread start actions.CThe maximum number of workers that the thread pool can have active.LThe number of currently active workers which are not processing a work item..The number of currently active worker threads.<An indication as to whether or not a new thread was started.&Page Request/Response between servers.Type of message.0The ID of the database file of the page request. The ID of the page in the file..SOS_Result of the page request.gNumber of pages to read ahead (request), number of pages that were not already in the BPool (response).Minimum LSN for the page read.LSN on the returned page.,Update the hardened LSN for a HADR database.Commit Policy.$Delay time in ms if policy is delay.PAPrior Hardened Log Block.New Hardened Log Block.ETransaction Commit harden still waiting for Hadron Commit management.%Elapsed time to so far in ticks = ms.Log Block waiting for harden.?Transaction Commit harden result from Hadron Commit management.&Elapsed time to process in ticks = ms.Result of the wait - 0 or 1+Lease with resource DLL valid flag - 0 or 1Log Block to wait for.Hardened Log Block.)Transaction Commit manager policy update."HADR partner commit policy update.Commit Policy Target.HADR partner sync state change. Sync state.PASync Log Block.0Test point for failure injection in Hadr Db Mgr.Test Point ID.Test Point value 1.Test Point value 2.2Test point for failure injection in Hadr Undo Mgr.=Test point for failure injection in Hadr Backup On Secondary.:Test point for failure injection in Hadr Auto Page Repair.GAmount of log scanned in Undo of Redo and Total log need to be scanned.&Amount of log remaining to be scanned.'Total amount of log need to be scanned./File Metadata Request/Response between servers. The start scan database file id.Type of file requested.SOS_Result of the scan.Number of files returnedPA2Hit/miss ratio for the compressed log block cache.Number of cache hits.Number of cache misses.-Number of cache insertion attempts that miss.Backup Sync message.#Sub Type of the Backup Sync MessageBackup Info message.SOS_Result of the request. Backup LSN)Last active transaction LSN at the backupMin skip LSN for FS log backup.3Occurs when HADR FileStream transport opens a file.2The error number value of the file open operation.%The mode in which the file is opened.The absolute path of the file.4Occurs when HADR FileStream transport closes a file.3The error number value of the file close operation.&The mode in which the file was opened.WOccurs when HADR FileStream transport finds relevant log records when interpreting log.=The identifier of the database that the log block belongs to.1The total number of log records in the log block.<The number of filestream chunk log records in the log block.=The number of transaction abort log records in the log block. The identifier of the log block.KOccurs when HADR FileStream transport has completed processing a log block.>The identifier of the database that this log block belongs to.:Occurs when HADR FileStream transport creates a directory.9The error number value of the directory create operation.#The absolute path of the directory.AOccurs when HADR FileStream transport detects message corruption.0The error number of message corruption detected.>The error message with details of message corruption detected.PAAOccurs when HADR FileStream transport traces a block end message.#The scan generation of the message.+The size of the message in number of bytes.The type of file transfer.AThe identifier of the log block that this message corresponds to.HOccurs when HADR FileStream transport traces a directory create message.,The identifier of the root of the directory.=The identifier of the transaction that created the directory.9The path of the directory relative to the root directory.BOccurs when HADR FileStream transport traces a file write message.'The identifier of the root of the file.1The offset of the data to be written to the file./The size of the data to be written to the file.)The flags corresponding to the file data.9The identifier of the transaction that wrote to the file.4The path of the file relative to the root directory.PA5Occurs when HADR FileStream transport flushes a file.3The error number value of the file flush operation.9Occurs when HADR FileStream transport sets end of a file.8The error number value of the set end of file operation.The size of the file.EOccurs when HADR FileStream transport detects inplace update to undo.?The identifier of the database that this file block belongs to.BThe identifier of the transaction that tracked the inplace update.GIdentifies if the end of log LSN from the primary is requested as well.sHADR Windows Server Failover Clustering change notifier starts receiving Availability Group specific notifications.LUnique identifier of the SQL Server object associated with the notification.HADR Availability Group ID.fHADR Windows Server Failover Clustering change notifier encountered a severe error and will terminate.NSQL error number returned from Windows Server Failover Clustering API wrapper.XHADR Windows Server Failover Clustering change notifier received a cluster notification.5Windows Server Failover Clustering notification type.bHADR Windows Server Failover Clustering will bring an availability group listener resource online.$HADR Availability Group Listener ID.%Availability group listener DNS name.LHADR is about to rollback availability group listener WSFC resource changes.\HADR set the WSFC dependency between an availability group and its listener resource object.9WSFC dependency expression between AG and its VNN object.6Could not create a hadron availability group listener.BDNS Name used in the availability group listener creation attempt.@The availability group listener TCP/IP port number was modified.tEnd of API that creates/opens SQL Server instance name to cluster node name map key in the cluster store (registry).%Whether the map key is newly created.1Cluster node to SQL Server instance map key name.PEnd of API that creates/updates a SQL Server instance to cluster node map entry.Full SQL Server instance name.-Windows Server Failover Clustering node name.HEnd of API that deletes a SQL Server instance to cluster node map entry.PAHADR Windows Server Failover Clustering change notifier detected that the local cluster node is not online. Change notifier will terminate.First attempt to bring a HADR Availability Group resource online failed. SQL Server will retry the operation at regular intervals.SQL Server has either exhausted all retry attempts, or Windows Server Failover Cluster has accepted the command to bring a HADR Availability Group resource online.#HADR Availability replica API call.4HADR Availability Group replica manager is starting.&HADR Availability Group state in Wsfc.>Occurs when the state of the Availability Replica has changed.+The state of the replica before the change.*The state of the replica after the change.!The ID of the Availability Group.#The name of the Availability Group.#The ID of the Availability Replica.FOccurs when the state of the Availability Replica Manager has changed.2The current state of Availability Replica Manager.2HADR Availability Group database replica API call.&HADR Availability Group Lease Renewal.PAOccurs when there is a connectivity issue between the cluster and the Availability Group resulting in a failure to renew the leasetHADR availability replica mutex acquisition state for synchronization of ar manager startup and shutdown operations._HADR availability replica critical section entry state (point of interest for tracing/testing).HADR availability group mutex acquisition state (point of interest for tracing/testing) for accessing local availability group config data.JHADR Database Replica has been fully unjoined from the Availability Group.?Occurs when secondary is going to append a log block to logmgr.'The ID of the log block to be appended.%The size of log block to be appended.4The sequence number being acknowledged by secondary.rRepresents a specific point in the tracing of a log block. This number is used by the Microsoft development team.-Occurs when primary has captured a log block.'The ID of the log block being captured.)The size of the log block being captured.KIndicates the sequence number of the log block being sent to the secondary.EThe sequence number of the log block to be accepted by the secondary. The size of the log block queue.!The ID of the availability group.*The ID or the target availability replica.KOccurs when primary has captured a log block which starts new virtual file.$log block id which starts a new VLF.file id for the new VLF.5Occurs when secondary is going to apply a VLF header.hadron database id6Occurs when primary or secondary DBR is changing statehadr availability replica id#HADR availability group resource ID@Occurs when primary send or secondary receives logblock message.&Id of log block being sent in message.0Sector count of log block being sent in message.-Byte size of log block being sent in message.-Logblock sequence ack sent back by secondary.+Log scan generation passed in from partner.PABytes in log block message.WOccurs after a log block message has been sent. This event is only used for failpoints.'Success or failure of the message send.AOccurs when primary send or secondary receives vlfheader message.-Id of log block being sent in header message.&Virtual file status in header message."Virtual file id in header message.%Physical file name in header message.$Logical file name in header message.)Bytes in virtual log file header message.-Occurs when secondary sends progress message.!Last log block sent to secondary.1Sector count of last log block sent to secondary.-Flow control sequence ack number for primary.&Redo thru log block set at apply side.Rate of redo at secondary.PARecovery queue at secondary.0Log scan generation from secondary apply object.IFlag to indicate if new watermark is being sent in this progress message.Log block id being redone last.-LSN of log block being hardened at secondary.Log manager truncation LSN.End of log LSN on secondary .+Occurs when primary sends progress message."Pending log scan queue at primary.%Common redo LSN from all secondaries.3Occurs when sync secondary sends a progress message'The log block ID for this hardened LSN.fOccurs when we're crafting a message to send containing a new hardened LSN on a secondary. Test only.Locally hardened LSN HADR DBIDRemote Availability Replica IDRedo Target LSN Redone Time Redo rateRedo queue size Commit TimeAG IDSecondary AR ID Database IDLog Truncation LSN Hardened LSNUndo LSNOldest Xact LSNStart of log LSNRedo LSNEnd of log LSN Commit LSNPA Shipped LSN Log Scan LSNSOccurs when evaluating read-only routing information on a local primary DB replica._True if the read-only routing list (READ_ONLY_ROUTING_LIST) set on the current primary is emptyxTrue if the selected destination read-only replica is the local primary replica (routing read-only workloads to primary)True if the read-only routing list (READ_ONLY_ROUTING_LIST) is not empty but none of the replicas in the list are available for routing (replica must allow readers and be synchronizing/synchronized){The selected destination read-only routing replica port (derived from the READ_ONLY_ROUTING_URL of the destination replica)The selected destination read-only routing replica host name (derived from the READ_ONLY_ROUTING_URL of the destination replica).The routing primary's availability database ID The routing primary's replica ID+The routing primary's availability group ID5A read-only routing operation successfully completed.The TCP-IP port returned to the client in the routing response. The port is determined using the READ_ONLY_ROUTING_URL set on the destination replica.The read-only routing server name returned to the client in the routing response. The server name is determined using the READ_ONLY_ROUTING_URL set on the destination replica.The read-only routing operation failed. This is sent when the primary replica has a READ_ONLY_ROUTING_LIST configured and none of the replicas in the list are available for read-only routing.DOccurs when AlwaysOn DDL is executed including CREATE, ALTER or DROPPA7Indicates the type of DDL action: create, alter or drop?Indicates the phase of DDL operation: begin, commit or rollback+The text of the statement that was executedpWhen set to 0, collect_statement disables collection of statement. By default the statement column is generated. The id of the availability group"The name of the availability groupOccurs when the failover validates the readiness of replica as a primary. For instance, the failover validation will return false when not all databases are synchronized or not joinedQIf the value is TRUE, then automatic failover will be invalidated on this replicaRIf the value is FALSE, then automatic failover will be invalidated on this replica The ID of the Availability Group"The name of the Availability Group"The ID of the Availability ReplicaMetadata cache entry addedMetadata cache entry flushedMetadata cache entry updatedMetadata entry version updatedPA!Metadata manager catalog inserted Metadata manager catalog updated Metadata manager catalog deletedMetadata agent catalog updatedMetadata cache vlr postedMetadata initiate lock objectMetadata manager lock objectMetadata agent lock objectMetadata lock objectMetadata initiate unlock objectMetadata unlock objectJMetadata add the segmentid column into secondary indexes of matrixdb heaps.Attempting to lookup a metadata object by nameTracing RemoveFromCache callersFailed HRESULTEvent used for LIKE tests onlyPATime taken to acquire a latchAddress of latch being acquired'Duration to acquire latch in CPU cycles$Number of samples collected thus far(Number of times page has been referencedTotal duration for all samples2Threshold in CPU cycles to trigger latch promotion Page file IDPage ID&Parallel scan with IO affinity started$Parallel scan with IO affinity ended'Parallel scan worker started processing(Parallel scan worker finished processing"Parallel scan subrange information!Parallel scan advances read ahead'Parallel scan read ahead position fixupPA/HoBt Schema Manager Startup/Shutdown operations#HoBt Schema Manager HoBt operations%HoBt Schema Manager column operations.HoBt Schema Manager allocation unit operations(HoBt Schema Manager HoBt page operations.HoBt Schema Manager HoBt attributes operationsPage is being looked upAsynchronous log write startLog write completeLog write had to retry Target block to redo through setRedo stop point setRedo stop point clearRedo thread done with work-Redo thread has entered to poll for redo workRedo thread is leavingPARedo on a log recordGenerate a log record>Log record generation stall for outstanding writes to complete)Indicates the database hitting the limit./Indicates the number of log writes outstanding..Indicates the log bytes pending to be written.0Occurs when a log block is cached into Log Pool.1ID of the database which the log block belongs to ID of the log block being cached"Size of the log block being cached'Whether the log block is read from disk#Whether the log block is incomplete#Whether the log block is read ahead?ID of the log consumer the log block is private to, 0 if shared)Pointer of the corresponding cache buffer6Occurs when a log cache buffer is replaced or removed.PA2ID of the database which the log blocks belongs to6ID of the first log block in the buffer being uncachedsID of the last log block in the buffer being uncached; 0 for a private cache buffer containing incomplete log blockAID of the log consumer the log blocks are private to, 0 if shared>Weight for a shared cache buffer; 0 for a private cache buffer5Occurs when a log block is consumed by a LogConsumer.8ID of the database which this log block is consumed from"ID of the log block being consumedID of the log consumer$Size of the log block being consumedfOccurs when the indicator on whether any LogConsumer is interested in new log to be generated changes.8ID of the database whose new log interest bit is flipped"Whether interest in new log is setQOccurs along with a log consumer's log consumption activity during its life time.5ID of the database which this log consumer belongs toID of the activityPAjOccurs along with the persistence status of a log block in a shared cache buffer being reset to persistent2ID of the database which this log block belongs toID of the log blockLID of the log consumer which resets the persistence status of this log block]Occurs along with a log block in a shared cache buffer being moved within the replacement set-Weight of the cache buffer before being moved,Weight of the cache buffer after being moved4New position of the cache buffer: 'H' head, 'T' tailVOccurs along with a cache buffer's reference counter being incremented or decremented.8ID of the database which this cache buffer holds log for0ID of the starting log block in the cache bufferlID of the ending log block in the cache buffer, 0 for a private cache buffer containing incomplete log block'I' increment, 'D' decrement=Occurs along with a log consumer's reading a log block ahead.;Occurs when log pool receives a memory status notification.Memory status value'Internal counter maintained by log pool&Occurs when a disk log read is issued.+ID of the database which the log belongs to'ID of the starting log block being readWhether the log is read ahead7ID of the log consumer the log being read is private to'Occurs when a disk log read is ignored.4Occurs when a log consumer is initialized or closed.!Whether the log consumer is aliveName of the log consumerOccurs when the request for a lock was canceled, such as when the query requesting the lock was canceled. Use this event to monitor locks.?The ID of the object that requested the lock that was canceled.aThe amount of time (in microseconds) between when the lock was requested and when it was canceledOccurs when a request for a lock times out because another transaction holds a blocking lock on the required resource. The time-out duration is determined by the @@LOCK_TIMEOUT system function. Use this event to help troubleshoot blocking issues.UThe time (in microseconds) between when the lock was requested and when it timed out.yOccurs when an attempt to acquire a lock generates a deadlock. This event is raised for each participant in the deadlock.PAThe deadlock chain session ID.Occurs when a fine-grain lock is converted into a coarser-grain lock, such as when a row lock is converted into an object lock. Use this event to monitor how locks are being used on the server.!The cause of the lock escalation.;The ID of the table for which the escalation was triggered.KThe ID of the HoBT (heap or B-tree) for which the escalation was triggered.zThe total number of locks that were converted. These locks are deallocated because they are covered by the escalated lock._The number of locks on the HoBT (heap or B-tree) at the time that the lock escalation occurred.EThe text of the Transact-SQL statement that triggered the escalation.sWhen set to 1, collect_statement enables collection of statement. By default the statement column is not generated.AOccurs when a request for a lock times out because of a blocking lock that is being held by a different resource. This event is identical to lock_timeout, but excludes cases in which the time-out value is 0, such as when lock probes are used. Time-outs with a duration of 0 do not necessarily indicate a blocking problem.<Global Lock Manager: Starting global lock acquire operation.4Database for which global lock request was received.2object (database or table) of global lock request.Source of global lock request.4The requested lock mode for the global lock request.:Global Lock Manager: Ending global lock acquire operation.<Global Lock Manager: Starting global lock release operation.:Global Lock Manager: Ending global lock release operation.LGlobal Lock Manager: Primary database segment acquire lock request received.IGlobal Lock Manager: Primary database segment acquire response generated.5The response lock result for the global lock request.LGlobal Lock Manager: Primary database segment release lock request received.IGlobal Lock Manager: Primary database segment release response generated.6Database for which global lock response was generated.JGlobal Lock Manager: Local database segment acquire lock request received.GGlobal Lock Manager: Local database segment acquire response generated.JGlobal Lock Manager: Local database segment release lock request received.GGlobal Lock Manager: Local database segment release response generated.FGlobal Lock Manager: Primary database segment undo responses received.5Number of responses received from the undo operation.RGlobal Lock Manager: Primary database segment undo request generated an exception.GGlobal Lock Manager: Local database segment undo lock request received.PADGlobal Lock Manager: Local database segment undo response generated.aGlobal Lock Manager: Exception event fired at AcquireDBLock to monitor proper exception handling.Database reference type.Timeout value requested.Database lock option.Global lock policy requested.$Error number for the exception event)The severity level of the exception eventError state codeaGlobal Lock Manager: Exception event fired at ReleaseDBLock to monitor proper exception handling.dGlobal Lock Manager: Exception event fired at AcquireTableLock to monitor proper exception handling.ADatabase of the table for which global lock request was received.1Table for which global lock request was received.dGlobal Lock Manager: Exception event fired at ReleaseTableLock to monitor proper exception handling.Occurs when a query uses a bitmap filter and the bitmap filter is disabled. Use this event to troubleshoot performance problems for queries with bitmap filters, and to identify queries where the bitmap filter was disabled because it is nonselective.The node ID of the root of the hash operator that is involved in the repartition. This corresponds to the Node ID in Showplan execution plan output.#Bitmap preferred memory calculationBitmap runtime tracejOccurs when a SQL Server transaction is coordinated through Microsoft Distributed Transaction Coordinator.'The isolation level of the transaction.3The state of the transaction coordination with DTC.(The ID of the transaction that was used.fThe binary representation of the Unit of Work ID that uniquely identifies this transaction within DTC.Occurs every time that SQL Server executes a SELECT, INSERT, UPDATE, or DELETE statement. Use this event to monitor if a query is running in parallel. The number of CPUs that were used to complete the process. A value of 0 indicates a serial plan that is running in serial, 1 indicates a parallel plan that is running in serial, and 2 or larger indicates a parallel plan that is running on the specified number of CPUs.-The type of statement that is being executed.The workspace memory (in kilobytes) that the process was granted to perform operations that involve hashing, sorts or create index operations. The memory is acquired during execution, as needed.Occurs when a SQL Server transaction begins, completes, rolls back or executes a savepoint. Use this event to monitor transaction behavior when troubleshooting applications, triggers or stored procedures.KThe amount of time (in microseconds) that the transaction has been running.7The state of the transaction that triggered this event.'Indicates a System or User transaction.The ID of the transaction.PA;The name of the object being referenced by the transaction.sThe name of the savepoint that triggered the event. This is only populated when the transaction_state is savepoint.)Occurs when a table or index scan starts.CThe database ID of the index or table for which a scan has started.1The ID of the table for which a scan has started.1The ID of the index for which a scan has started.AThe ID of the HoBT (heap or B-tree) for which a scan has started.2The database name of the index/table being scanned(Occurs when a table or index scan stops.7The database ID of the index or table that was scanned.%The ID of the table that was scanned.%The ID of the index that was scanned.5The ID of the HoBT (heap or B-tree) that was scanned.?The number of logical page reads that occurred during the scan.@The number of physical page reads that occurred during the scan.2Occurs when a record is added to the SQL Server transaction log. This is a very high volume event that will affect the performance of the server. Therefore, you should use appropriate filtering to reduce the number of events, and only use this event for targeted troubleshooting during a short time period.qThe ID of the database that generated the log record. This field is populated based on the operation field value.BThe transaction ID of the operation that generated the log record.,The size of the log record that was written.=Indicates the type of log operation that generated the event.aProvides additional context for the log operation, such as the type of object for this operation.eThe replication command that was used. This is only relevant for the LOP_REPL_COMMAND log operation .bThe time when the transaction started. This field is populated based on the operation field value.The ID of the current allocation unit that generated the log record. This field is populated based on the operation field value.Occurs when there is insufficient memory to process the build input of a hash join. This results in either a hash recursion when the build input is partitioned, or a hash bailout when the partitioning of the build input exceeds the maximum recursion level. Use this event together with any of the query_pre_execution_showplan or query_post_execution_showplan events to determine which operation in the generated plan is causing the hash warning.<Indicates either a hash recursion or a hash bailout warning.yIdentifies the node ID of the operation that caused the hash warning. This corresponds to the Node ID in Showplan output.GIndicates the number of times that the build input was sub-partitioned.Occurs when a T-SQL statement or stored procedure waits more than one second for a memory grant or when the initial attempt to get memory fails. Use this event in combination with events that identify waits to troubleshoot contention issues that impact performanceuThe amount of time (in microseconds) that the query had to wait for the memory grant. Only valid for warning_type = 1DIndicates the type of the problem that causes the memory grant delay<An XML document that describes the Server-wide memory grantsWhen set to 1, collect_server_memory_grants enables collection of server_memory_grants. By default the server_memory_grants column is not generated.Occurs when the sort operation on an executing query does not fit into memory. This event is not generated for sort operations caused by index creation, only for sort operations in a query. (For example, an Order By in a Select statement.) Use this event to identify queries that perform slowly because of the sort operation, particularly when the warning_type = 2, indicating multiple passes over the data were required to sortTIndicates whether sorting a query required a single or multiple passes over the dataOccurs when the batch operation to build a hash table encounters low memory condition and switches to row mode operation. Use this event to identify performance issues due to low memory condition.(Node ID of the hash table build operator6Maximum memory limit for this batch plan segment in KBOccurs when a query tries to get more memory grant during execution. Failure to get this additional memory grant may cause the query slowdown.(The size of requested memory grant in KBYThe actual granted memory in KB. This can be zero if this additional grant request fails.7ID of resource pool where this grant request belongs toOccurs when the server memory usage increases or decreases by more than either 1 megabyte (MB) or 5% of the maximum server memory, whichever is larger. Use this event to identify periods of increased memory usage on the server.6Indicates whether memory usage increased or decreased.,Indicates the new memory size, in megabytes.Occurs when any of the data or log files for a database changes size. Use this event to monitor changes to the size of database files.RThe amount of time (in microseconds) required for the file size change to complete7The ID of the database owning the file that is modifiedPA#The ID of the file that is modifiedGIndicates whether the modified database file is a data file or log file?Indicates whether the file size change is automatic or explicit5Resulting total file size (in KB) after the operationoIndicates the file size change (in KB). This is a positive number for file growth, and negative for file shrink-The logical name of the file that is modified9The name of the database owning the file that is modifiedOccurs when the memory communication buffers for a query with multiple Parallelism operators become full, resulting in one of the operators writing to TempDB. If this happens multiple times in a single query plan the query performance is impacted. Use this event in conjunction with any of the *_showplan events to determine which operation in the generated plan is causing the exchange spill using the node_id fieldLIdentifies the node_id of the operation that caused the exchange spill event8Indicates if this is the beginning or the end of a spill\Occurs when a task has been blocked longer than the time that is specified by the sp_configure blocked process threshold setting. This event is not triggered by system tasks or by tasks that are waiting for non-deadlock-detectable resources. Use this event to troubleshoot blocked processes. (By default, blocked process reports are not generated.)5The time (in microseconds) that the task was blocked.=The database ID of the object on which the lock was acquired.4The ID of the object on which the lock was acquired.The ID for the index on the object that was affected by the event. To determine the index ID for an object, use the index_id column of the sys.indexes system view.#The type of lock that was acquired.PA>The ID of the transaction in which the blocked process exists..The type of the object that acquired the lock.0An XML graph that describes the blocked process.>The database name of the object on which the lock was acquireduOccurs when the state of a database mirror has changed. Use this event to monitor the condition of a database mirror./Indicates the new state of the database mirror.3Indicates the initial state of the database mirror.2Provides a description of the mirror state change.Occurs during an online index build process to indicate the progress of the build operation. Each stage of an online index build operation generates an event. Use this event to monitor online index builds.:The stage in the build operation that generated the event.@The database ID of the object for which an index is being built.8The ID of the object for which the index is being built.(The ID of the index that is being built.HThe time (in microseconds) that the current stage takes to be completed.The number of rows that are inserted. This field is only populated when build_stage field value is equal to 6 (Inserted row count).The worker thread ID (nonzero if parallel plan). This field is only populated when build_stage field value is equal to 6 (Inserted row count).PAaThe name of the index that is being built. This field is only populated when not building a heap.:The name of the object for which the index is being built.7The database name of the object having it's index built(Occurs when a page is added to the suspect_pages table in the msdb database. This event is issued asynchronously from the insertion of a corresponding page into the suspect_pages table. Therefore, a job that is listening to this event may not find the correlating suspect_pages entry immediately.6The ID of the database that contains the suspect page.;The ID of the database file that contains the suspect page.eThe ID of the suspect page. This is the same as the page_id column in the suspect_pages system table.'The error that caused the suspect page.3Name of the database that contains the suspect pageOccurs when Resource Governor detects that a query has exceeded the CPU threshold that is specified for REQUEST_MAX_CPU_TIME_SEC. The detection interval is five seconds. The event is guaranteed to detect the queries that exceed the threshold by at least five seconds. If a query exceeds the threshold by less than five seconds, the detection might be missed, depending on the timing of the query and the time of the last detection sweep.jThe CPU time (in microseconds) that was used by the last request in the process that caused the violation.8The session ID of the process that caused the violation.?The resource group ID of the process that caused the violation.&Process an invalidate cache log recordCache Type to invalidation./Keys used to invalidate particular cache entry.Page allocated Page freedzOccurs when new extents are allocated during index building. Use this event to indentify how extents are used by an index.,internal id of the extents allocating thread(file id the thread allocate extents fromnumber of extents allocated7number of non-continous sections of this set of extents&first extent id of this set of extentsdPre-allocating new cache range for a Sequence object.See system view sys.sequences for more details.HID of a Sequence object. See system view sys.sequences for more details.+Last persisted value for a Sequence object.kOccurs when the extent activation cache has reached its max size and we have to go into overflow mechanism.(current max size of the extent Id cache.;how many extent activation are currently in overflow state.Occurs immediately before QVM context is serialized and shipped, and immediately after it is received and deserialized. Use this to get a dump of shipped/received QVM context data.+Identifier indicates where the dump occurs.Occurs immediately before QVM context is serialized and written back, and immediately after it is received and deserialized. Use this to get a snapshot of writeback QVM context data.LOccurs whenever some context that fits in Int64 is accessed from within QVM.:Occurs whenever CDbAndSetOpts is accessed from within QVM..ThreadCache node was successfully checked out.|Occurs when an expression is not natively supported in batch processing mode and a wrapper of row-by-row evaluation is used.Returns a set of counters associated with the Process performance object. The event occurs once every 15 seconds for both the SQL Server and SQL Agent processes.rShows the percentage of elapsed time that the threads of the process have spent executing code in privileged mode.xShows the percentage of elapsed time that all of the threads of this process used the processor to execute instructions.hShows the percentage of elapsed time that this process's threads have spent executing code in user mode.YShows the current size, in bytes, of the virtual address space that the process is using.`Shows the maximum size, in bytes, of virtual address space the process has used at any one time.EShows the current number of bytes in the working set of this process.Shows the size of the working set, in bytes, that is used for this process only and not shared nor sharable by other processes.ZShows the maximum size, in bytes, in the working set of this process at any point in time.The name of the processpReturns a set of counters associated with the System performance object. The event occurs once every 15 seconds.PAdShows the percentage of the Total Registry Quota Allowed that is currently being used by the system.7Shows the rate of alignment faults fixed by the system.hShows the combined rate at which all processors on the computer are switched from one thread to another.@Shows the rate at which exceptions are dispatched by the system.File Control Bytes/sec shows the overall rate at which bytes are transferred for all file system operations that are neither read nor write operations, including file system control requests and requests for information about device characteristics or status.Shows the combined rate of file system operations that are neither read nor write operations, such as file system control requests and requests for information about device characteristics or status.ZShows the combined rate of read and write operations on all logical disks on the computer.Shows the overall rate at which bytes are read to satisfy file system read requests to all devices on the computer, including read operations from the file system cache.Shows the combined rate of file system read requests to all devices on the computer, including requests to read from the file system cache.Shows the overall rate at which bytes are written to satisfy file system write requests to all devices on the computer, including write operations to the file system cache.Shows the combined rate of file system write requests to all devices on the computer, including requests to write to data in the file system cache.>Shows the rate of floating emulations performed by the system.GThe number of processes in the computer at the time of data collection.3Shows the number of threads in the processor queue.mShows the combined rate of calls to Windows system service routines by all processes running on the computer.cShows the total time, in seconds, that the computer has been operational since it was last started.DThe number of threads in the computer at the time of data collectionReturns a set of counters associated with the Logical Disk performance object. The event occurs once every 15 seconds for each hard or fixed disk drive.cShows the percentage of time that the selected disk drive is busy servicing read or write requests.ZShows the percentage of time that the selected disk drive is busy servicing read requests.[Shows the percentage of time that the selected disk drive is busy servicing write requests._Shows the percentage of the total usable space on the selected logical disk drive that is free.IThe percentage of time during the sample interval that the disk was idle.SShows the average number of bytes transferred from the disk during read operations.bShows the average number of bytes transferred to or from the disk during write or read operations.RShows the average number of bytes transferred to the disk during write operations.{Shows the average number of both read and write requests that were queued for the selected disk during the sample interval.lShows the average number of read requests that were queued for the selected disk during the sample interval.FShows the average time, in seconds, of a read operation from the disk.9Shows the time, in seconds, of the average disk transfer.EShows the average time, in seconds, of a write operation to the disk.mShows the average number of write requests that were queued for the selected disk during the sample interval.PAhShows the number of requests outstanding on the disk at the time that the performance data is collected.bShows the rate at which bytes are transferred to or from the disk during write or read operations.SShows the rate at which bytes are transferred from the disk during read operations.BShows the rate at which read operations are performed on the disk.LShows the rate at which read and write operations are performed on the disk.RShows the rate at which bytes are transferred to the disk during write operations.CShows the rate at which write operations are performed on the disk.gShows the unallocated space, in megabytes, on the disk drive. One megabyte is equal to 1,048,576 bytes.AThe rate at which I/Os to the disk were split into multiple I/Os.The logical disk drive nameReturns a set of counters associated with the Processor performance object. The event occurs once every 15 seconds for each processor in the system.KThe percentage of time the processor spends in the C1 low-power idle state.KThe percentage of time the processor spends in the C2 low-power idle state.KThe percentage of time the processor spends in the C3 low-power idle state.Shows the percentage of time that the processor spent receiving and servicing deferred procedure calls (DPCs) during the sample interval.HThe percentage of time the processor is idle during the sample interval.PA}Shows the percentage of time that the processor spent receiving and servicing hardware interrupts during the sample interval.<The percentage of the current processor's maximum frequency.eThe percentage of elapsed time that the processor spends executing threads that are not low priority.IShows the percentage of non-idle processor time spent in privileged mode.wShows the percentage of time that the processor is executing application or operating system processes other than Idle.KShows the percentage of non-idle processor time that is spent in user mode.9The rate that the CPU enters the C1 low-power idle state.9The rate that the CPU enters the C2 low-power idle state.9The rate that the CPU enters the C3 low-power idle state.Shows the rate at which deferred procedure calls (DPCs) are added to the processor's DPC queue between the timer ticks of the processor clock.gShows the overall rate at which deferred procedure calls (DPCs) are added to the processor's DPC queue.iShows the average number of hardware interrupts that the processor is receiving and servicing per second.0Represents whether a processor is parked or not.4The frequency of the current processor in megahertz.Processor State Flags.The processor name.PAtOccurs when an operator outputs significantly more rows than estimated by the Query Optimizer. Use this event to identify queries that may be using sub-optimal plans due to cardinality estimate inaccuracy. Using this event can have a significant performance overhead so it should only be used when troubleshooting or monitoring specific problems for brief periods of time.Operator node identifier. Use this value to locate the operator in the XML query plan/graphical plan using the NodeId attribute.Worker thread number for parallel query plan, or zero for serial query plan. The cardinality estimate inaccuracy is detected on per-worker thread basis, considering the total number of rows estimated for this operator and assuming equal distribution of rows across the worker threads.Number of rows estimated by the Query Optimizer for this operator, divided by the actual degree of parallelism (number of worker threads).:Actual number of rows output by this worker thread so far.Number of times this event has already fired for the same query and operator. Larger values will mean more significant cardinality estimate inaccuracy.Occurs when a spool is opened.-Identifies the node id of the spool operator.0Identifies whether the spool is a primary spool./Identifies whether the spool is a hybrid spool.0Identifies whether the spool is a segment spool.4Identifies whether the spool is a multiparent spool./Identifies whether the spool is an eager spool.0Identifies whether the spool implements a stack.EIdentifies whether the workfile of the spool needs to be kept around.:Identifies whether the spool is an index-on-the-fly spool.PA5Identifies whether the spool is an index-cache spool.8Identifies whether the spool has a one-row optimization.4Identifies whether the spool supports large objects.6Identifies whether the spool prefetches large objects.BIdentifies whether the spool requests only one row from its child.2Identifies whether the spool executes in parallel.\Occurs when a secondary spool is opened before primary for the first time or after a rebind.7Identifies the node id of the secondary spool operator.5Identifies the node id of the primary spool operator.;Identifies whether the primary spool has never been opened.8RPC thread cache Session Context generated for shipping.5Remote context is being initialized for thread cache.<Occurs when a Window Spool operator uses on-disk work table.The node ID of the Window Spool operator using an on-disk work table. This corresponds to the Node ID in Showplan execution plan output.AOccurs when a filter eliminates column store segment during scan.0High order element of the ID of the transaction./Low order element of the ID of the transaction.=The ID of the rowset of the column store index being scanned.EThe ID of the column store segment that has been skipped during scan.VOccurs when a list of filters for column store index is pushed down to storage engine.YIndicates whether the list of filters has exceeded the size limit and has been truncated.+An XML document describing list of filters.OOccurs when we issue read-ahead for a rowgroup during a scan on a column store. Rowgroup IdThe hobt id for the columnstore<The accessor id being used in the scan (Identifies the scan)IOccurs when we issue read for a rowgroup during a scan on a column store.DOccurs when batch hash join uses separate hash column in hash table.!Node ID of the hash join operatorAOccurs when cleanup has started for online index build with LOBs.-The database id for the object being cleaned.+Original rowset for the online index build.PA1Tracking table rowset for the online index build.,Secondary rowset for the online index build.BOccurs when cleanup has finished for online index build with LOBs.+Bad memory detected by the operating system:The number of bad pages detected in the current iteration.>Database page with bad memory detected by the operating system&The database id that had the bad page.!The address of the corrupted page*The database file id that had the bad page3The page in the database file that had the bad page9Flag indicating if the bad page was a clean or dirty page*Name of the database that had the bad page0Name of the database file that had the bad page.<Occurs just before deleting all the extended recovery forks.FThe id of the database to which the extended recovery forks belong to.=Occurs just before deleting the recovery LSN in the metadata.<The id of the database to which the recovery LSN belongs to.Occurs during updating secondary's recovery forks stack. After deleting extra entries in the secondary stack but before copying new entries from primary.Occurs during updating secondary's recovery forks stack. After updating the stack but before saving the recovery LSN in the metadata.UOccurs after deleting secondary's stack entries but before copying primary's entries.PA PAPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGX<00<0 +70 0!0 +TɉktJϠu'00 aj0  *H 0y1 0 UUS10U Washington10URedmond10U Microsoft Corporation1#0!UMicrosoft Code Signing PCA0 111101223917Z 130201224917Z01 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR10UMicrosoft Corporation0"0  *H 0 é|#1%uyϓKa%wKZmI17t`N%X N-:e.[]u4P!}9D#fe 6`*dȇE(WY&Jl)2?% oj-:mf16p@v.G+e+_hE xkP5[qa! EeI~7Z߸v Q*P:c܁G00U% 0 +0UqÏv, J(0U0U#0WEt]CT-2H0VUO0M0KIGEhttp://crl.microsoft.com/pki/crl/products/MicCodSigPCA_08-31-2010.crl0Z+N0L0J+0>http://www.microsoft.com/pki/certs/MicCodSigPCA_08-31-2010.crt0  *H yiȏk`|>8Rϙ-=au8NY?C|Sb֨vuYl?/~9T'X5aymQWcrf9*35 ^15E ]Ǘ*:IHE26m nvUU4y]n̗h}i{ U}M0b{젒*W)HͶ! b 5_kԱwRw?lV\6N^z 1ynr_0W|UplxC 500 a0  *H 0w1 0 UUS10U Washington10URedmond10U Microsoft Corporation1!0UMicrosoft Time-Stamp PCA0 110725204219Z 121025204219Z01 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR1'0%U nCipher DSE ESN:9E78-864B-039D1%0#UMicrosoft Time-Stamp Service0"0  *H 0 ;SDzMVqSw7~>Sѱ"unav; CS b83+={EW c4bFٞ9Uw5\HOCX8lKzn`[?:? }m/X}ʊ89h-X#*Z їE7 |ӶSx#!bZjipS4%1UL5[ɫS)_,%d'u 00Uy# U,h)bg68Z0U#0#4RFp @v+50TUM0K0IGEChttp://crl.microsoft.com/pki/crl/products/MicrosoftTimeStampPCA.crl0X+L0J0H+03kir|_%D5( Րap-o,ݹ0qxȩg z ¼W?i00&Ԟ{ IERu{".VϩN< :ŭj"#l'~2y%B❅WY/-&)ųׅ`Z{{^4Km'Тѐ }|4lJDyh(" ,Ha#00 +70UWEt]CT-2H0 U0U00U#0`@V'%* SY䤡ca0_10 &,dcom10 &,d microsoft1-0+U$Microsoft Root Certificate AuthorityyJLsX.e0PUI0G0ECA?http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl0T+H0F0D+08http://www.microsoft.com/pki/certs/MicrosoftRootCert.crt0vU o0m0k +7/0^0\+0PNCopyright 2006 Microsoft Corporation.0U% 0 +0  *H 0 b9&a=ܬƙІ.2e^">ֆ趟ʋ;u >LdtIglfF:FBȑ7$AwO_R/>V[uSTie$%MPO "Y"t E{YL`xѺk~D@ҽKnU8HUz }۔/{kdO,4)] 8/ V1i΅ ֮8 nOL)) \\V#W &6Do阵sx\pax@WB-E;+%-NۭZI9Fh͋HٮXx(yap\'w{XͦENѭ~2T8'_(טϼ>{̺B֕s{tvd= h%0u,bIA0hffn_L7P5#0hIe\2SN0ؑDc~$Eա#u0 *H  1 000w1 0 UUS10U Washington10URedmond10U Microsoft Corporation1!0UMicrosoft Time-Stamp PCA a0+]0 *H  1  *H 0 *H  1 120211160119Z0# *H  1,̖.,<3.60  *H \G7 5-%EWp:ah2JA#;| LDl-9&Ҟmʾ`Dvx} o_NJ2oD )sƥRy1Ώ$z ctCZzk5,vMX`AHO8"K&~a9GB{fxUC3_o3*gp:<^11u *Ǹ [P`盞LQe!>m 00 aIU 0  *H  0~1 0 UUS10U Washington10URedmond10U Microsoft Corporation1(0&UMicrosoft Code Signing PCA 20100 111010204524Z 130110205524Z01 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR10UMicrosoft Corporation0"0  *H 0 Ϥ01QU4`E)_++rC\;*Yqrx ,8[b}ԯaD9βTK&DOW#Jjة6w4O{_u9}aRƲ~:xȔ=G'rpW0'ca(лbd@"+^wrN|U~\~@6tdW$XkUgZ.i;%00U% 0 +0Ui1bqXxa0U#0_{"XrN!t#20VUO0M0KIGEhttp://crl.microsoft.com/pki/crl/products/MicCodSigPCA_2010-07-06.crl0Z+N0L0J+0>http://www.microsoft.com/pki/certs/MicCodSigPCA_2010-07-06.crt0 U00  *H  x[Zm#}u j'EӒNħe݅ JSxA 0 T'Yh8.?iL Lx P:M?+R=Mk&Z\j@K1(|Tp?vY0nm. $X9MRlj[AS{T1 DA~Ri?c2KW8X—@c-mk|+;B+9@"QpA `&ǩc؅0p0X a RL0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1200U)Microsoft Root Certificate Authority 20100 100706204017Z 250706205017Z0~1 0 UUS10U Washington10URedmond10U Microsoft Corporation1(0&UMicrosoft Code Signing PCA 20100"0  *H 0 dPyg LVhDXOv|mE9eҏDe,U}.+A+KnILk‰q͵K̈k:&?4W]I*.ՅY?+t+;FFIfTUbWrg% 4]^(ղcӲȊ& Y5LR[ HwօGj-\`ƴ*[#_Eo73jMjfcx0ϕ00 +70U_{"XrN!t#20 +7  SubCA0 U0U00U#0Vˏ\bh=[Κ0VUO0M0KIGEhttp://crl.microsoft.com/pki/crl/products/MicRooCerAut_2010-06-23.crl0Z+N0L0J+0>http://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0U 00 +7.00=+1http://www.microsoft.com/PKI/docs/CPS/default.htm0@+042 Legal_Policy_Statement. 0  *H  tWO){xP" 4*,Ͽ4ہ5oywNaZ#bQEg?<09@!)奡i"tGCS0i% moar,iv=Qۦ9H7amS˧a¿⃫k}(QJQlȷJi~IprGc֢DciFz?!{#-A˿Lﱜ"KInv[Sy=s5SP8f3'9x6N_=GS a=*ג,7Z>@B1V$]Qjy{%qDj#u1000~1 0 UUS10U Washington10URedmond10U Microsoft Corporation1(0&UMicrosoft Code Signing PCA 2010 aIU 0  `He0 *H  10 *H  1  +70 +7 10  +70/ *H  1" EW2ۛF…h Н(_OG0R +7 1D0B SQL Server 2012http://www.microsoft.com/sql0  *H nCL4W8zmtiޕ古Ald)sak nFpq/I3b(wrttФ\s{٘~v0TN?F>93ALA??<\kyʶG+2Y*Q\`Cc Try%G!q' S}I48fMx6*]c[wȠsstM0 +710 *H 01 0 +0* *H  0 +Y 0!0 +]ݰ"Ȝ]JR7S:O1&"z20120211160121.339Z001 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR1'0%U nCipher DSE ESN:936C-7AEE-74AE1%0#UMicrosoft Time-Stamp Service0q0Y a *0  *H  01 0 UUS10U Washington10URedmond10U Microsoft Corporation1200U)Microsoft Root Certificate Authority 20100 100701213655Z 250701214655Z0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 20100"0  *H 0  w: iktTե |hK,_av>f+[S'1A |a0Y0D`TC M8Bݓs0W&E GͿ$`2X`FXG2tag_TϓLĦ]an(aF'$gr!KdPb]w=WuBM@Q>gfD~Knʱz* 1N5xhttp://www.microsoft.com/pki/certs/MicRooCerAut_2010-06-23.crt0U 00 +7.00=+1http://www.microsoft.com/PKI/docs/CPS/default.htm0@+042 Legal_Policy_Statement. 0  *H  Q ?q=!o1Wm0fjxǨ%kTW+QDS`v@@A\\^5$VKtBȯ7}Z?yJR8/ye٩kzoK0D$"<Y)p2J'U/3b_W@ΙfjbJ &9Jqc{!mÜ<}jxm8ؔƥ B"8 %d~cY%z.9Wvqa˚Gͧ};q ]t"aڰPo1:eGxHr~akow˧ 9؂r*T9[ Uzs;-3.)/T'!ȬN(ۖBAM*f0ӻt2Kc{/!YDǘP5Gj+ἃdPeMsؾHu84YR䇉 ;G+ TH9Hkd~"AH6/S4J&)IaʱX&_" wguaS+ƶwp/%B:2AOTlE {@PFWƀb00U?9v5#[LW70U#0c:\1C{|F3hZmU0VUO0M0KIGEhttp://crl.microsoft.com/pki/crl/products/MicTimStaPCA_2010-07-01.crl0Z+N0L0J+0>http://www.microsoft.com/pki/certs/MicTimStaPCA_2010-07-01.crt0 U00U% 0 +0  *H  O)KSQ\\s*8hO9KC54Ud" `΃ ;@|D[ifa?ann!ҲgR*ru1>QI̐Ԉ!kbب"pQØ9X=pD.mLsT&cYNOg~u:TePbɂ%=e?cbӉ_ɩVK@TA%X,O㣏)}Wrxnj] PLv0^0㡁01 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR1'0%U nCipher DSE ESN:936C-7AEE-74AE1%0#UMicrosoft Time-Stamp Service% 0 +^$3+b xc ցs적001 0 UUS10U Washington10URedmond10U Microsoft Corporation1 0 U MOPR1'0%U nCipher NTS ESN:B027-C6F8-1D881+0)U"Microsoft Time Source Master Clock0  *H ϣ0"20120211112939Z20120212112939Z0t0: +Y 1,0*0 ϣ000 !#06 +Y 1(0&0  +Y  0 0 0  *H *Aܚ}kpEK)pin_f\P0a:>uѣ{77y X&2pR"V>zi]s^FxB>c3n*dQ9ΤMpEh Dh-ak8I65΢kvg};du;OJ-(N!vm cPU\d6F!nkBD$>r;,!D]_H7ı!^"z#|RS5]1000|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 2010 aN 0 +0 *H  1  *H  0# *H  1zw3n #i;0 *H   1000^$3+b xc ցs00~0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 2010 aN 0ZǕ. Ԥ@0  *H a8F lD2hAꆩoPxw=ew |*\_Z{Z8A|GZ?vFI˷:-(=TߌQi3_]Ƒ;͘^JICi4U.J}HǬW´ ГsTo6"b)bvjp\)ك(&Bֻ p>m8 ?[t ~ "WRus DxXV5$$]yxZ:c Vex''+,Pk~^