MZ@ !L!This program cannot be run in DOS mode. $Uu]333c3c3Rich3PEd5O"  X@X<.rsrc@@ 3(@Xp     0H`x 8Ph !"#$(%@&X'p()*+,-./00H1`2x3         0 @ P ` p             0 @ P ` p               0  @  P  `  p                 ld"&N4,8l2P7>t \HPV DZ>bRjp lz x$ ̕. ĥ  hT | L> 0T  f % 2AV N Z6(m v tx  n@TZT8 (,TZGlobally Unique IDEvent schema version ETW Channel(Extended events for Microsoft SQL ServerEvent grouping keywords'Stored procedure or SQL statement state Event pair&Indicates the phase of a DDL operation@Broker transmission outgoing acknowledgement state machine event@Broker transmission outgoing acknowledgement state machine stateABroker transmission outgoing acknowledgement state machine actionBroker dialog state-trees in different stages during optimization$Names of features disabled in MatrixBackground job failure types+Indicates the status of a statistics update8The method used to remove the object from the plan cache>The type of object that contains the statement being compiled.-Query notification background thread activity(Query notification subscription activity+Query notification parameter table activity$Query notification template activityBroker activation stateBroker conversation actionBroker route typeBroker message sourceBroker message typeBroker mirror route stateBroker acknowledgement type'Return value from remote procedure callReason for statement recompileDatabase SQL statement typedml change process stage&Reason for a fulltext issued recompile4Indicates the phase of HADRON DDL failover operationEThe reason why Hekaton parameter passing code took the slow code pathColumn store object0Broker transmission delivery state machine event0Broker transmission delivery state machine state1Broker transmission delivery state machine actionBroker transmission timer0Broker transmission object worktable load resultSQL Server shutdown optionBackground job typesError reporting categories Object typeFull-text crawl operationDistribution Policy Type&Bucket hint used to group dump reports>Identifies different types of connectivity ring buffer recordsDIdentifies the connection source of connectivity ring buffer records)Component which is reporting health stateComponent's stateXDefines the event types for which the Matrix Configuration Manager serves notifications.3Session Manager: Defines the priority of work item./Session Manager: Defines the type of work item.8Session Manager: session footprint creation or deletion.Notification event typeNotification event contextLogical filegroup type>Reason for ALTER TABLE ADD column to do an UPDATE on every row Scroll optionPAError destinations*Broker activation stored procedure invokedAssociated Keyword$Broker activation task limit reachedBroker activation task abortedBroker activation task startedDA message was enqueued into a Service Broker transmission body table%referenced by transmission queue rows-number of referencing transmission queue rowsDA message was dequeued from a Service Broker transmission body tableYOccurs when no receive activity is detected on an activated queue with available messagesThe ID of the alerting queue.5The ID of the database containing the alerting queue.#Time in seconds since last receive.7The name of the database containing the alerting queue.When set to 1, collect_database_name enables collection of database_name. By default the database_name column is not generated.Cursor manager cursor beginCursor manager cursor endCursor manager cursor cache hit"Cursor manager cached cursor added$Cursor manager cached cursor removed"Cursor manager cursor memory usage)Cursor manager cursor worktable use begin'Cursor manager cursor worktable use end Cursor manager cursor plan beginCursor manager cursor plan end.Databases bulk copy rows (due to bcp activity):Databases bulk copy throughput in KB (due to bcp activity)8Metadata change notification received from the framework'Database distribution policy is changed*Occurs when a database transaction begins.(Occurs when a database transaction ends.Databases data file size changePlan cache cache hitSQL statement starting1Occurs when a Transact-SQL statement has started.FIndicates whether the starting of the statement triggered a recompile.EThe statement line number, in relation to the beginning of the batch.FThe statement start offset, in relation to the beginning of the batch.qThe statement end offset, in relation to the beginning of the batch. The value will be -1 for the last statement.3The text of the statement that triggered the event.pWhen set to 0, collect_statement disables collection of statement. By default the statement column is generated.SQL statement completed3Occurs when a Transact-SQL statement has completed.AThe time (in microseconds) that it took to execute the statement.KIndicates the CPU time (in microseconds) that is consumed by the statement.DThe number of physical page reads that were issued by the statement.CThe number of logical page reads that were issued by the statement.;The number of page writes that were issued by the statement6The number of rows that were touched by the statement.&The last row count for this statement.CThe plan handle of the cache entry of the parameterized query plan.When set to 1, collect_parameterized_plan_handle enables collection of parameterized_plan_handle. By default the parameterized_plan_handle column is not generated.#Stored procedure statement starting>Occurs when a statement inside a stored procedure has started.cThe ID of the database that owns the module that contains the statement that has started executing.MThe ID of the module that containst the statement that has started executing.VThe type of the module that contains the statement that has started started executing.The nesting level of execution.FThe statement line number, in relation to the beginning of the module.GThe statement start offset, in relation to the beginning of the module.rThe statement end offset, in relation to the beginning of the module. The value will be -1 for the last statement./The name of the object that owns the statement.yWhen set to 1, collect_object_name enables collection of object_name. By default the object_name column is not generated.$Stored procedure statement completed@Occurs when a statement inside a stored procedure has completed.dThe ID of the database that owns the module that contains the statement that has finished executing.MThe ID of the module that contains the statement that has finished executing.OThe type of the module that contains the statement that has finished executing.<The number of page writes that were issued by the statement. RPC starting0Occurs when a remote procedure call has started.zThe option that is used to reset the connection. This field is available only for reset connection remote procedure calls.HThe name of the object that was referenced by the remote procedure call.DThe text of the statement that was run by the remote procedure call.OThe remote procedure call binary stream that is used for the replay of a trace.yWhen set to 1, collect_data_stream enables collection of data_stream. By default the data_stream column is not generated. RPC completed2Occurs when a remote procedure call has completed.OThe time (in microseconds) that the remote procedure call took to be completed.PThe number of physical page reads that were issued by the remote procedure call.OThe number of logical page reads that were issued by the remote procedure call.0The return value from the remote procedure call.CThe number of rows that were returned by the remote procedure call.{The option that was used to reset the connection. This field is available only for reset connection remote procedure calls.NThe name of the object that was being referenced by the remote procedure call.HThe output parameters that were returned from the remote procedure call.When set to 1, collect_output_parameters enables collection of output_parameters. By default the output_parameters column is not generated.Plan cache cache attemptOccurs when an ALTER TABLE ADD column operation results in an UPDATE that affects every row. This event signals a potentially expensive DDL statement.&The ID of the table that was modified.?Reason that causes the ALTER TABLE to have to UPDATE every row.#Cursor manager cursor cache attemptAppDomain ring buffer recordedvWhen set to 1, collect_call_stack enables collection of call_stack. By default the call_stack column is not generated.#Security error ring buffer recordedPAError has been reported!Occurs when an error is reported.VIndicates whether the error was a user-defined error (true) or a system error (false).The error category.The error destination.NIndicates whether the error was intercepted by a Transact-SQL TRY/CATCH block.Trace message publishedErrorlog written+External Key Management external API calledStart of module executionsWhen set to 1, collect_statement enables collection of statement. By default the statement column is not generated.End of module execution,FILESTREAM file I/O streaming access requestWhen set to 1, collect_workitem_description enables collection of workitem_description. By default the workitem_description column is not generated.The identifier for the transaction within which the event occured. Use this value to lookup information in the filestream_transaction_id column in dm_filestream_file_io_requests or dm_filestream_file_io_handles.When set to 1, collect_transaction_id enables collection of transaction_id. By default the transaction_id column is not generated.PAWhen set to 1, collect_correlation_ids enables collection of correlation_ids. By default the correlation_ids column is not generated.|When set to 1, collect_logical_path enables collection of logical_path. By default the logical_path column is not generated.When set to 1, collect_physical_path enables collection of physical_path. By default the physical_path column is not generated.When set to 1, collect_original_path enables collection of original_path. By default the original_path column is not generated.:Response to a FILESTREAM file I/O streaming access request,FILESTREAM file I/O streaming access failure8FILESTREAM file I/O streaming access tracing information)FILESTREAM file I/O streaming access dumpAOccurs when a write completion for a FILESTREAM file is received.4Broker transmission delivery state machine event endBroker transmission timer setBroker transmission timer resetBroker transmission timer fire&Broker transmission lazyflusher submit0Broker transmission lazyflusher processing begin.Broker transmission lazyflusher processing endPABroker transmission timer armed&Broker transmission lazyflusher removeBroker transmission object load/Broker transmission object worktable load begin-Broker transmission object worktable load end/Broker transmission object worktable save begin-Broker transmission object worktable save end:Broker transmission outgoing ack state machine event begin:Broker transmission outgoing ack state machine action fire8Broker transmission outgoing ack state machine event end6Broker transmission delivery state machine event begin6Broker transmission delivery state machine action fire?A message was enqueued into a Service Broker transmission queuemessage size in bytes)non-0 value references a message body row?A message was dequeued from a Service Broker transmission queueOccurs 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 of SQL Server.:The ID of the deprecated feature that triggered the event.The unlocalized user-friendly name of the deprecated feature that triggered the event. The deprecated feature will be removed from a future version of SQL Server, but not the next major release.VThe localized message that suggests a workaround or the use of an alternative feature.]Occurs when you use a feature that will be removed from the next major release of SQL Server.The unlocalized user-friendly name of the deprecated feature that triggered the event. The deprecated feature will be removed from the next major release of SQL Server.+query optimizing (intermediate) result treeUnpin index descriptionThe database this index is in.The object which is affected.%The index description being unpinned.BAn intrinsic operator identified in output tree (Matrix-specific).AIndicates the type of intrinsic operator found in QO output tree.&DML change based MD cache refresh info0The ID of the database that changed table is in.MThe object which is changed (and possibly whose MD cache needs to refreshed).PA#Number of rows changed in this dml.Matrix V1 Unsupported FeatureJA new service broker instance is being added to broker instance hash-table(Occurs when SQLExit() routine is invokedpProfiles compile time. Equivalent to a combination of SQL Trace event 'Execution Warnings' and trace flag -T8783Compile time in milliseconds8Occurs when a Transact-SQL batch has finished executing.1The CPU time (in milliseconds) used by the batch.EThe amount of time (in microseconds) that the batch took to complete.6The number of physical page reads issued by the batch.5The number of logical page reads issued by the batch.)The number of rows returned by the batch.,Indicates the execution result of the batch. The text of the batch being run.sWhen set to 0, collect_batch_text disables collection of batch_text. By default the batch_text column is generated.7Occurs when a Transact-SQL batch has started executing.-The text of the batch that is being executed.DOccurs when a prelogin containing a traceid arrives on a connection.'The sequence number sent by the client.%The connection id sent by the client.#The activity id sent by the client.Occurs when a successful connection is made to the Server. This event is fired for new connection or when connections are reused from a connection poolBReuse of cached connection from connection pool or new connection?>Is this connection a Dedicated Administrator Connection (DAC)?Connect database ID+Network packet size used for the connection=Provides a list of the SET options passed with the connection|When set to 1, collect_options_text enables collection of options_text. By default the options_text column is not generated.Connect database nameOccurs when a successful connection to the Server is reported to Windows using the User Access Logging API. This event is only fired for new connections. Connection resets are not tracked.1The HResult returned by the UAL API function callVGUID used for Software Usage Metrics. This indicates the role for the database engine.'IP address of the user's client machine Login name{Occurs when a user has logged out of (logged off) the Server. This event is required in traces that will be used for Replay>Connection is cached in connection to pool or complete logout?JIndicates if this connection is a Dedicated Administrator Connection (DAC)=The amount of time (in microseconds) since the user logged inZIndicates the amount of CPU time (in microseconds) consumed by the user during the sessionGThe number of physical page reads issued by the user during the sessionFThe number of logical page reads issued by the user during the session?The number of page writes issued by the user during the sessionIndicates that a cancel operation, client-interrupt request, or broken client connection has occurred. Be aware that cancel operations can also occur as the result of implementing data access driver time-outs.;The elapsed time (in microseconds) of the interrupt action.The request ID (or logical connection ID). A value of 0 indicates the default batch in a non-MARS (multiple active result sets) scenario.(Occurs when an Extended Events session is started. To avoid duplicate (or secondary) existing_connection events when other Extended Events sessions are started, we recommend that you always use this event with the following predicate: WHERE started_event_session_name = 'your_event_session_name'.!The session ID of the connection.OIndicates whether the connection is a dedicated administrator connection (DAC).*The current database ID of the connection.CThe network packet size (in bytes) that is used for the connection.NThe number of active transactions (transaction nest level) for the connection.(The resource group ID of the connection.4The time (in microseconds) since the user logged on.The client process ID.GProvides a list of the SET options that are passed with the connection.RThe name of the Extended Events session that was started and triggered this event.+The current database name of the connectionThe client application name.The client hostname.The NT domain. The NT user.The session NT domain.The session NT user."The name of the Server Prinicipal.PA!The SID of the Server Prinicipal.=The name of the Server Principal that originated the session.<The SID of the Server Principal that originated the session.2Occurs when the Server has been started or stopped8Indicates the type of operation that triggered the event/Indicates whether the activity succeeded or notOccurs when a stored procedure is not found in the procedure cache. Frequent occurrences of this event could indicate that SQL Server needs more memory. Use this event along with other sp_cache_* events to troubleshoot issues caused by the procedure cache.FThe ID of the database containing the object being sought in the cache9The ID of the stored procedure being sought in the cache.1The type of the object being sought in the cache.^The name of the object being sought in the cache. This is populated when object_name is blank.yWhen set to 1, collect_cached_text enables collection of cached_text. By default the cached_text column is not generated._The text of the SQL statement that will be cached. This is populated when cached_text is blank.IThe name of the database containing the object being sought in the cache.Occurs when a stored procedure is inserted into the procedure cache. Use this event together with other sp_cache_* events to troubleshoot issues that are caused by the procedure cache.8The type of the object that was inserted into the cache.PAQThe ID of the database that contains the object that was inserted into the cache.6The ID of the object that was inserted into the cache.uThe name of the object that was inserted into the cache. This field is not populated for ad hoc and prepared queries.qThe Transact-SQL text that was inserted into cache. This field is only populated for ad hoc and prepared queries.GThe name of the database containing the object inserted into the cache."The plan handle of the cache entryyWhen set to 1, collect_plan_handle enables collection of plan_handle. By default the plan_handle column is not generated.Occurs when a stored procedure is removed from the procedure cache. Use this event together with other sp_cache_* events to troubleshoot issues that are caused by the procedure cache.7The type of the object that was removed from the cache.PThe ID of the database that contains the object that was removed from the cache.5The ID of the object that was removed from the cache.BThe method that was used to remove the object from the plan cache.tThe name of the object that was removed from the cache. This field is not populated for ad hoc and prepared queries.tThe Transact-SQL text that was removed from the cache. This field is only populated for ad hoc and prepared queries.FThe name of the database containing the object removed from the cache.Occurs when a stored procedure is retrieve from the procedure cache. Use this event along with other sp_cache_* events to troubleshoot issues caused by the procedure cache.@The ID of the database containing the object found in the cache.2The ID of the stored procedure found in the cache.*The type of the object found in the cache.hThe text of the statement that was retrieve from the cache. This is populated when object_name is blank.]The name of the object retrieved from the cache. This is populated when cached_text is blank.BThe name of the database containing the object found in the cache..Occurs when a plan is shipped to another brick(The brick id we are shipping the plan to>The start offset for the statement whose plan we are receiving<The end offset for the statement whose plan we are receiving=The plan handle of the parent cache entry on the source brick1Occurs when a plan is recieved from another brick+The brick id of the brick who sent the planCThe plan handle of the cache entry the query plan was inserted intoFOccurs when an object was created by the CREATE statement. This event is raised two times for every CREATE operation. The event is raised when the operation begins and when the operation is either rolled back or committed. Add the nt_username or server_principal_name actions to this event to determine who altered the object.>The ID of the database that contains the object being created.PA&The ID of the object that was created.(The type of the object that was created.%The ID of the index that was created.@The ID of an object that is related to the object being created.DIndicates the phase of the DDL operation: begin, commit or rollback.(The ID of the transaction that was used.(The name of the object that was created.<The name of the database containing the object being createdBOccurs when an object was deleted by the DROP statement. This event is raised two times for every DROP operation. The event is raised when the operation begins and when the operation is either rolled back or committed. Add the nt_username or server_principal_name actions to this event to determine who altered the object.>The ID of the database that contains the object being deleted.&The ID of the object that was deleted.(The type of the object that was deleted.%The ID of the index that was deleted.@The ID of an object that is related to the object being deleted.(The name of the object that was deleted.<The name of the database containing the object being deletedOccurs when a statement is defined for a cursor, the cursor properties are set, and the cursor is populated. Use this event to troubleshoot cursor performance issues.-Indicates the type of cursor that was opened.RThe ID that is used by ODBC, OLE DB, or DB-Library to coordinate server execution.Occurs when index and column statistics are automatically updated. This event can be generated multiple times per statistics collection when the update is asynchronous.4The ID of the database that is specified by the job.2The object for which statistics are being updated.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 number that represents the job ID.)Indicates the type of the background job.'Indicates the statistics update status.EThe time (in microseconds) that is required to update the statistics.8Indicates the number of retry attempts if the job fails.7Indicates whether the statistics update was successful.[Indicates the last error number if the final attempt to update statistics was unsuccessful.Indicates the number of statistics that were affected by the operation. This field is populated only when the status field equals 1.qThe list of statistics that were updated or created. This field is populated only when the status field equals 1.%Name of the database specified by jobOccurs when a statement that contains a cursor declaration is compiled into an execution plan, but before the cursor is opened. Use this event to troubleshoot cursor performance issues.[Occurs when a Transact-SQL statement was prepared by SQLClient, ODBC, OLE DB or DB-Library.$The handle of the prepared statementdOccurs when a prepared Transact-SQL statement was executed by SQLClient, ODBC, OLE DB or DB-Library.%The handle to the prepared statement.pOccurs when a prepared Transact-SQL statement was unprepared (deleted) by SQLClient, ODBC, OLE DB or DB-Library.oOccurs when a cursor is created and executed. This event is used for troubleshooting cursor performance issues.4Indicates the type of cursor that is being executed.}Occurs when an execution plan that contains a cursor is recompiled. Use this event to troubleshoot cursor performance issues.Occurs when a cursor is converted to a different cursor type because the requested cursor does not support the statement that is being executed. This event is used to troubleshoot cursor performance issues.HIndicates the type of cursor that resulted from the implicit conversion.MIndicates the type of cursor that was originally requested for the operation.|Occurs when an execution plan that contains a cursor is discarded. Use this event to troubleshoot cursor performance issues.fOccurs when a cursor is deallocated. This event is used for troubleshooting cursor performance issues.Occurs when a query accesses a column that does not have statistics available that could have been useful for query optimization. Use this event to identify queries that may be using sub-optimal plans. This event is only generated when the Auto Create Statistics option is turned off.PA:Provides the list of columns that have missing statistics.yWhen set to 1, collect_column_list enables collection of column_list. By default the column_list column is not generated.Occurs when an executed query is missing a join predicate. Use this event to identify a query that may perform slowly because of the missing predicate. This event only occurs if both sides of the join return more than one row.>Occurs when a DML operation that is intended to overwrite only part of a large column value is forced to rewrite the entire value. This happens if the table's heap or clustered index is being built online. Use this event to identify DML workloads that are running more slowly as a result of building an index online.XThe stage of processing when the event is raised. The event can be raised either when the DML plan is compiled or when it is executed. Use this data field to filter the event: To see if the problem has occurred at least once, request only compile-time events. To see how often the problem has occurred, request only non-compile-time events.2Occurs when sp_trace_generateevent is called. Use this event to monitor user-defined events in your application code during testing or execution. The data that is returned from user_event includes the event_id that was specified in the call to sp_trace_generateevent. This can be a value between 82 and 91.[The event_id that is specified in the call to the sp_trace_generate_event stored procedure.mContains the value of the @userinfo parameter that was passed to the sp_trace_generateevent stored procedure.mContains the value of the @userdata parameter that was passed to the sp_trace_generateevent stored procedure.Occurs when an OLEDB Call to a remote provider returns an error. Use this event to view the Hresult returned from failed OLEDB Calls*The HResult returned by the OLEDB provider Error message(The name of the Linked Server was called4The name of the OLEDB provider used to make the call2The name of the OLEDB method used to make the call4The parameters sent and received from the OLEDB callPA3Occurs when SQL Server calls on OLEDB provider for a distributed query or remote stored procedure. Use this event to monitor OLEDB calls that do not return data or that do not use the QueryInterface method. This event will be trigged twice for each OLEDB call, once when it starts and once when it completes?Shows if this is the Start or Complete event for the OLEDB callHThe amount of time (in microseconds) required to complete the OLEDB callOccurs when SQL Server calls on OLEDB provider for a distributed query or remote stored procedure. Use this event to monitor OLEDB calls that use the QueryInterface method. This event will be trigged twice for each OLEDB call, once when it starts and once when it completesOccurs when SQL Server calls on OLEDB provider for a distributed query or remote stored procedure. Use this event to monitor OLEDB calls that make data requests to the OLEDB provider. This event will be trigged twice for each OLEDB call, once when it starts and once when it completesReports the progress of a Service Broker conversation. This event occurs when specific actions that are defined in the conversation_action field occur.<The action within the conversation that triggered the event.8The role of the conversation handle in the conversation.JReturns the current state of the conversation when the event is triggered.The ID of the conversation dialog. This ID is transmitted as part of the message and is shared between both sides of the conversation.&The handle of the conversation dialog.8The conversation group that the conversation belongs to.3The name of the service that initiated the message.:The name of the service broker that initiated the message.4The name of the remote service for the conversation.-The ID of the remote service broker instance.!The name of the service contract.COccurs when Service Broker creates or deletes a conversation group.EIndicates whether the conversation group is being created or dropped.!The ID of the conversation group..Occurs when Service Broker forwards a message.-The fragment number of the forwarded message.0The sequence of the message in the conversation.NThe number of hops remaining for the message to reach its destination service.>The time to live value (in seconds) for the forwarded message.The amount of time (in seconds) that the message has been alive. When this value is greater than or equal to the time_to_live, the message is dropped."The type of the forwarded message.7The name of the service that the message was sent from.6The name of the source broker service for the message.5The name of the service that the message was sent to.;The name of the destination broker service for the message.MOccurs when Service Broker drops a message that was intended to be forwarded.PAjThe error number of a given event. Typically, this error number is stored in the sys.messages system view.*The severity level of the exception event.-The error state code for the exception event.5The role of the Service Broker for this conversation.>The Time to Live value (in seconds) for the forwarded message.The time (in seconds) that the message has been alive. When this value is greater than or equal to the time_to_live field value, the message is dropped.The ID of the conversation dialog. This ID is transmitted as part of the message, and is shared between both sides of the conversation.+A description of why a message was dropped.The type of the forwarded message. The message type is defined by using the CREATE MESSAGE TYPE Transact-SQL command when you configure Service Broker.8The error number for the delayed message classification.The source of the message.3The role of the message source in the conversation.EThe type of route that Service Broker has determined for the message.9The error message for the delayed message classification.<The next Service Broker instance on the route to the target.EThe network address of the next Service Broker instance in the route.9The name of the service that the message will be sent to.UOccurs when an exception is encountered during the processing of transmission objectsWThe error number of a given event. Often this is the error number stored in sysmessages)The severity level of the exception eventError state code7The role of the transmission object in the conversation/The ID of the conversation in this transmission/Occurs when a Service Broker queue is disabled.+The ID of the user queue that was disabled.tOccurs every time Service Broker receives an open or close connection request from either of the mirrored instances.4Indicates whether the mirrored route is operational.2The Service Broker endpoint address of the server.3The error message that is returned from the server.'Indicates the server role in mirroring.GOccurs when Service Broker sends or receives a message acknowledgement.JIndicates how Service Broker sent or received the message acknowledgement.PAJThe role of the Service Broker instance that is acknowledging the message.>The fragment number of the message that is being acknowledged.EThe fragment number of the message that contains the acknowledgement.KThe sequence of the message in the conversation that is being acknowledged.RThe sequence of the message in the conversation that contains the acknowledgement.'The priority level of the conversation.PThe current value of the HONOR_BROKER_PRIORITY database option for the database.lOccurs when a full-text crawl (population) is started. Use this event to monitor full-text crawl operations.7Indicates that a full-text crawl operation has started.=The ID of the object on which the full-text crawl is running.@The ID of the database in which the full-text crawl was started.MThe name of the database containing the object on which the crawl is running.lOccurs when a full-text crawl (population) is stopped. Use this event to monitor full-text crawl operations.>The ID of the object on which the full-text crawl has stopped.@The ID of the database in which the full-text crawl has stopped.,Occurs when a Service Broker message cannot be delivered. This can occur for several reasons, such as the target Service Broker is unreachable, the target queue is unavailable, the message is out of order, there are time-outs because of in-memory lists, or there is a failure to classify the message.:The fragment number of the acknowledgement in the message.#The fragment number of the message.:The sequence number of the acknowledgement in the message.7The sequence number of the message in the conversation.The type of message.8The ID of the conversation to which the message belongs.(The reason that the message was dropped.8Occurs when Service Broker receives a corrupted message.:A description of the message corruption that was detected.Occurs when a Service Broker queue monitor starts an activation stored procedure, sends a QUEUE_ACTIVATION notification, or when an activation stored procedure exits.QIndicates the state of the activation stored procedure that triggered this event.2Indicates the number of active tasks on the queue.NIndicates the CPU time (in microseconds) that was required for the activation.FThe time (in microseconds) that was required for activation execution.-The ID of the queue that triggered the event.QThe number of physical read operations that were performed during the activation.PAPThe number of logical read operations that were performed during the activation.IThe number of write operations that were performed during the activation.The activation message. The message may contain the name of the activation stored procedure, messages that were passed back from the activation stored procedure, or an error message.DOccurs when an object was altered by the ALTER statement. This event is raised two times for every ALTER operation. The event is raised when the operation begins and when the operation is either rolled back or committed. Add the nt_username or server_principal_name actions to this event to determine who altered the object.?The ID of the database that contains the object being modified.'The ID of the object that was modified.)The type of the object that was modified.&The ID of the index that was modified.AThe ID of an object that is related to the object being modified.)The name of the object that was modified.=The name of the database containing the object being modifiedOccurs when a query plan is removed from the plan cache and the historical statistics for the object are about to be destroyed.The number of times the statement has been recompiled. This is only available when compiled_object_type is Query from Stored Procedure or BatchOnly available when compiled_object_type is Stored Procedure or Trigger. Then it is the object_id of the object being removed from the cache as it appears in sys.procedures and sys.triggers/sys.servertriggers respectively.PThe 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.MThe execution statistics for the object that is being removed from the cache.Occurs when a statement-level recompilation is required by any kind of batch. This includes stored procedures, triggers, ad hoc batches and queries. Batches may be submitted through several interfaces, including sp_executesql, dynamic SQL, Prepare methods or Execute methods.)The cause of the statement recompilation.FThe ID of the database that owns the statement that is being executed.The ID of the object that contains the statement that was recompiled. The object can be a stored procedure, trigger or user-defined function. For ad hoc batches or prepared Transact-SQL statements, object_id is blank.DThe class of object that contains the statement that was recompiled.The name of the object that contains the statement that was recompiled. The object can be a stored procedure, trigger or user-defined function. For ad hoc batches or prepared Transact-SQL statements, object_name is blank..The text of the statement that was recompiled.Occurs when a BEGIN TRANSACTION request that was sent from a client application through the transaction management interface has started.Occurs when a BEGIN TRANSACTION request that was sent from a client application through the transaction management interface has completed.CThe error number for any error that is associated with the request.(Indicates whether the request succeeded.Occurs when a PROMOTE TRANSACTION request that was sent from a client application through the transaction management interface has started.Occurs when a PROMOTE TRANSACTION request that was sent from a client application through the transaction management interface has completed.7The binary representation of the DTC transaction token.Occurs when a COMMIT TRANSACTION request that was sent from a client application through the transaction management interface has started.\Indicates that a new transaction will be started after the current transaction is committed.Occurs when a COMMIT TRANSACTION request that was sent from a client application through the transaction management interface has completed.5The error number that is associated with the request._Indicates whether a new transaction will be started after the current transaction is committed.Occurs when a ROLLBACK TRANSACTION request that was sent from a client application through the transaction management interface has started.hIndicates whether a new transaction will be started after the current rollback transaction is committed.Occurs when a ROLLBACK TRANSACTION request that was sent from a client application through the transaction management interface has completed.XThe error number for any error that is associated with the ROLLBACK TRANSACTION request.=Indicates whether the ROLLBACK TRANSACTION request succeeded.Occurs when a SAVE TRANSACTION request that was sent from a client application through the transaction management interface has started.Occurs when a SAVE TRANSACTION request that was sent from a client application through the transaction management interface has completed.DThe error number for any error that was associated with the request.2Occurs when a background job has ended abnormally.?The object for which statistics are being generated or updated.PA8Indicates the type of failure that occurred for the job.rIndicates the error number that caused the job to end. This applies only when the job_failure_type field equals 1.{Indicates the severity of the error that caused the job to end. This applies only when the job_failure_type field equals 1.xIndicates the state of the error that caused the job to end. This applies only when the job_failure_type field equals 1.5The time (in microseconds) since the job was started.{Indicates the number of retry attempts before the job is ended. This applies only when the job_failure_type field equals 1.Occurs when a connection is made to an OLE DB provider. This event collects properties from the remote provider from several property sets, including the following: DBPROPSET_DATASOURCEINFO, SQLPROPSET_OPTHINTS, DBPROPSET_SQLSERVERDATASOURCEINFO (SQL Server only), DBPROPSET_SQLSERVERDBINIT (SQL Server only), DBPROPSET_ROWSET, and the IDBInfo interface. Use this event to analyze and troubleshoot OLE DB provider calls in remote queries.The name of the linked server. The name of the OLE DB provider.CThe OLE DB provider information, such as capabilities and settings.Occurs when a request to load an assembly is executed. Use this event to troubleshoot queries that are running common language runtime (CLR) code to monitor server, database or user information that is related to loading the assembly.'The system-assigned ID of the assembly.GIndicates whether the assembly load succeeded (true) or failed (false).,The name of the assembly that is referenced.-Occurs when an XQuery expression is compiled.)The line number of the XQuery expression.6The statically inferred type of the XQuery expression.9The OLE DB method that was used by the XQuery expression.-Occurs when an operation is performed that is related to query notification subscriptions. Use this event to monitor when subscriptions are created or removed, when a subscription produces a notification message, and when errors occur while producing a notification message or deleting a subscription.XIndicates the type of activity that is being performed on the notification subscription.An XML document that provides information about the specific activity being performed on the notification subscription. The document conforms to the schema at http://go.microsoft.com/fwlink/?LinkId=63331.eOccurs when an operation is performed that is related to the parameter tables that are used in query notifications. Use this event to monitor operations that are related to creating and maintaining reference counts, and dropping the internal tables that store parameter information. This event also tracks when the usage count is reset on a parameter table.OIndicates the type of operation that is being performed on the parameter table.An XML document that provides information about the specific operation being performed on the parameter table. The document conforms to the schema at http://go.microsoft.com/fwlink/?LinkId=63331.Occurs when operations are performed related to the query templates used by the Database Engine to share information about a query used for notification. Use this event to monitor when a query template is created, used or destroyedDIndicates the type of activity being performed on the query templateReturns an XML document containing information specific to this event. The document conforms to the schema at http://go.microsoft.com/fwlink/?LinkId=63331Occurs when background activity to support query notifications is performed. Use this event to track subscription time-outs, pending subscription notification messages, and parameter table destruction.VIndicates the type of query notification background activity that triggered the event.An XML document that provides information about the specific background activity for query notifications. The document conforms to the schema at http://go.microsoft.com/fwlink/?LinkId=63331.Database created"HADRON DDL Alter AG failover statePAXOccurs when a LOGON trigger or a Resource Governor classifier function begins execution.TIndicates whether a user-defined classifier function or a LOGON trigger is executed.9The ID of the database that contains the executed object.The ID of the executed object. The type of the executed object. The name of the executed object.3Name of the database that contains the suspect pageZOccurs when a LOGON trigger or a Resource Governor classifier function finishes execution.eThe time (in microseconds) that was used by a LOGON trigger or Resource Governor classifier function.sIndicates the CPU time (in microseconds) that was used by a LOGON trigger or Resource Governor classifier function.The number of physical page reads that were issued during the LOGON trigger or Resource Governor classifier function execution.~The number of logical page reads that were issued during the LOGON trigger or Resource Governor classifier function execution.The number of page writes that were issued by the user during the LOGON trigger or Resource Governor classifier function execution./Indicates the error number, if an error occurs.5Indicates the state of the error, if an error occurs.*The name of the classified workload group.PA3Name of the database containing the executed objectOccurs when a plan is created for a query or batch that includes a plan guide. Use this event to determine when plan guides are successfully applied.The object ID of the module that was being executed when the plan was applied. If the guide was not applied in a module, this field is NULL.6The name of the plan guide that was used successfully.Occurs when an execution plan is created for a query or batch without using the provided plan guide. Use this event to identify queries and batches with invalid plan guides. Use the sys.fn_validate_plan_guide function to detect errors in the plan guide.1The name of the plan guide that was unsuccessful.vOccurs when a Transact-SQL batch is executed that was created for a specific situation and was not in the query cache.5The text of the Transact-SQL batch that was executed.[Occurs when a look up into the column store object pool cannot find the object in the pool..The database id for the object being looked up*The hobt id for the object being looked up,The column id for the object being looked up,The object id for the object being looked upSOccurs when an uncontained usage is detected during the compilation of a statement.@The object id of the module that owns the uncontained statement.LThe line number of the uncontained statement within the current T-SQL frame.PA[The name of the database that was either the source or the target of the uncontained usage.0The statement type of the uncontained statement.qAdditional information useful in locating the exact uncontained usage. For e.g. the three or four part name used.?The name of the uncontained feature exercised by the statement.?The type of the uncontained feature exercised by the statement.5authentication performance statistics: login function:authentication performance statistics: find login function9authentication performance statistics: create login tokenbSecurity Token Permission Caches have been invalidated by incrementing timestamp for the database.>Security Cache Object Permissions Cache has removed an object.*All entries in Security Cache are removed.?Security Cache Object Permissions Cache has inserted an object.)Occurs when a network packet is enqueued.6Occurs when a memory dump of the process is requested.Reason for stack traceQOccurs when there is a server-initiated connection closure, such as login failed.PA0Occurs when a new result set is being processed.WIndicates whether this event occurred in the start or end of the result set generation.<Time interval between result set generation in microseconds.,Occurs when a component state is determined.;XML field containing extra information regard the componentdWhen set to 1, collect_data enables collection of data. By default the data column is not generated.YTranslate full-text query to equivalant T-SQL query that works on a dummy fragment table.;The equivalent T-SQL query works on a dummy fragment table.DProduces a fulltext query execution statistics report in XML format.?An XML document describing fulltext query execution statistics..Fired when a fulltext test access point is hit7The id of the database with the fulltext indexed table."The table with the fulltext index.\Indicates the start of a fulltext reorganize operation for the table identified by table_id.The ID of the database.The ID of the table.PA<The total size in bytes of all the fulltext index fragments.!The number of fragments to merge.7The degree of parallelism to be used for the operation.5The number of partitions in the destination fragment.#The ID of the destination fragment.Reports a source fragment before running Phase1 of the reorganize operation. The process raises as many events of this type as there are source fragments.The ID of the fragment.pReports a fragment that has been selected as a source fragment by one of the Phase1 background merge work items.fReports a destination fragment that has been created by one of the Phase1 background merge work items.2Reports the reorganize progress for a given table. The ID of the table.7The percentage complete rounded to the closest integer.=Reports the reason for issuing recompile of a fulltext query.4 The ID of the object responsible for the recompile.|Reports the language used for each document by semantic indexing during a full-text crawl with statistical_semantics enabled The ID of the document.The ID of the column.8Was a statistical language model found for this documentpThe language ID of the statistical language model semantic indexing determined was a best-fit for this document.[Session Manager received a notification for an event such as brick-down, brick-rejoin, etc.-Brick on which the notification was received.7Specific event for which the notification was received.PSession Manager: A work item has been enqueued in the thread pool for execution.Type of the work item enqueued.Priority of the work item.Creation time of the work item.RSession Manager: A work item has been dequeued from the thread pool for execution.Type of the work item dequeued.5Session Manager: Starting the execution of work item. Type of the work being executed.$Priority of the work being executed..Creation time of the work item being executed.5Session Manager: Finished the execution of work item.Type of the work just executed.Session Manager: A session footprint was just created or deleted. This is used to trace session footprint creations and deletions. Session id.Session token.Incarnation_id of the brick.KType of the session footprint lifecycle event (i.e., creation or deletion).NDatabase DDL statement has been parsed and compiled, and start to be executed.RMetadata Id of the targeted database, or 0 if the id is not available at the time.IDatabase DDL statement finished run-time check, such as permission check.6Start to create a database segment at the local brick.3One database segment is created at the local brick.fAll files on one database segment are created, and primary file information is inserted into metadata.+All required database segments are created.@All database segment infos are created in masterDB on MDM brick..An ex-lock is acquired for dropping a databasePAYRemove global metadata from Master database, including sysdatabases and database segments'Database compatibility level is changed"The logical file group is created.Occurs when sp_repl_generateevent is called. this event is an internal repl event for tracing repl stored procedures. The data that is returned from user_event includes the event_id that was specified in the call to sp_repl_generateevent. This can be a value between x and y.ZThe event_id that is specified in the call to the sp_repl_generate_event stored procedure.lContains the value of the @userinfo parameter that was passed to the sp_repl_generateevent stored procedure.lContains the value of the @userdata parameter that was passed to the sp_repl_generateevent stored procedure.)Profiling function CSQLSource::Execute().cpu ticks spentfixed counter 0fixed counter 1fixed counter 2general counter 0general counter 1general counter 2general counter 3thread id of current worker&Profiling function HKProc::FExecute().'Profiling function UDFInvokeExternal().&Profiling function ExecUdfLobAccess().'Profiling function ExecUdxDataAccess().0Profiling function CTableValuedClrUdf::GetRow()..Profiling function CTableValuedClrUdf::Init().VOccurs when a look up into the column store object pool, finds the object in the pool._Occurs when an existing DQ session that matches the executing DQ is found in the session cache.9The ID of the remote server to which this call connected..The name of the Linked Server that was called.5The name of the OLEDB provider used to make the call.1The remote user ID used for the connection login.8The local windows user ID used for the connection login.BThe provider connectionstring property of the openrowset metadata.3The datasource property of the openrowset metadata.1The location property of the openrowset metadata.0The catalog property of the openrowset metadata._Occurs when no existing DQ session that matches the executing DQ is found in the session cache.:Occurs when a DQ session is stored into the session cache.;Occurs when a DQ session is removed from the session cache.-Occurs when the session cache is invalidated.nOccurs when an attempt to acquire global lock used before attempting to create a global IDataInitialize objectEOccurs when global lock for global IDataInitialize object is acquiredCOccurs immediately before global IDataInitialize object initializesMOccurs whenever global IDataInitialize object is returned to calling function%Occurs when Hekaton MATGen is invoked'Occurs when Hekaton SAL error is raisedVOccurs when a Hekaton procedure call dispatch goes to slow parameter passing code path-Occurs when an IPC call arrives to the serverCollect database IDCollect transaction IDPACollect session ID(Collects the name of the Server instanceCollect Transact-SQL stackCollect SQL textCollect plan handle'Create mini dump for the current thread&Create mini dump including all threadsCollect client application nameCollect client process IDCollect client hostnameCollect NT usernameCollect session's NT usernameCollect username(Collect current session resource pool ID)Collect current session resource group IDCollect current request ID)Collect whether current session is systemCollect current database name+Collect current transaction sequence numberCollect query hash. Use this to identify queries with similar logic. You can use the query hash to determine the aggregate resource usage for queries that differ only by literal valuesCollect query plan hash. Use this to identify similar query execution plans. You can use query plan hash to find the cumulative cost of queries with similar execution plansSCollects the SID of the Server Prinicipal in whose context the event is being firedbCollect the sql_handle for the current batch with line number, statement offsets and nesting level5Collect the same value as the CONTEXT_INFO() functiongCollects the name of the Server Principal that originated the session in which the event is being firedSCollects the name of the Server Principal in whose context the event is being firedHCollects the optional identifier provided at connection time by a clientRoute events to listeners.3Maximum number of callbacks that must be supported.<Pointer to a target pointer that will be set to this target.'Route events to asynchronous listeners.Get the current database IDGet the current transaction IDGet the current session ID'Get the current client application name!Get the current client process IDGet the current client hostnameGet the current NT domainGet the current NT user!Get the current session NT domainGet the current session NT userGet the current username$Get current session resource pool ID%Get current session resource group IDGet current request ID%Get whether current session is systemOGet the SID of the Server Prinicipal in whose context the event is being fired. Get SQL textGet the current database name2Get the same value as the CONTEXT_INFO() function.$Get the name of the Server instance.OGet the name of the Server Principal in whose context the event is being fired.cGet the name of the Server Principal that originated the session in which the event is being fired.Get plan handleGet Transact-SQL stack^Get the sql_handle for the current batch with line number, statement offsets and nesting level'Get current transaction sequence number`Use the query_hash to create a predicate that filters events based on queries with similar logicoUse the query_plan_hash to create a predicate that filters events based on queries with similar execution plansCGet the optional identifier provided at connection time by a client7Equality operator between two SQL UNICODE string values9Inequality operator between two SQL UNICODE string values8Less than operator between two SQL UNICODE string valuesALess than or Equal operator between two SQL UNICODE string values;Greater than operator between two SQL UNICODE string valuesDGreater than or Equal operator between two SQL UNICODE string values4Equality operator between two SQL ANSI string values6Inequality operator between two SQL ANSI string values5Less than operator between two SQL ANSI string values>Less than or Equal operator between two SQL ANSI string values8Greater than operator between two SQL ANSI string valuesAGreater than or Equal operator between two SQL ANSI string values3LIKE operator between two SQL UNICODE string values0LIKE operator between two SQL ANSI string values PAPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADX<00<0 +70 0!0 +!@8"94C^%@o00 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 ب<mZH]Zj7&mka6-JՠDM̝=ȏC#u0 *H  1 000w1 0 UUS10U Washington10URedmond10U Microsoft Corporation1!0UMicrosoft Time-Stamp PCA a0+]0 *H  1  *H 0 *H  1 120211160119Z0# *H  1-\"YH)0  *H M?y~*EqHZXDZ!ECS2а3R$+:63MB^2D: !7If @Y;jA%6Ue;3yv@RL|>ol!/MCmko1<]- BEncmn⶜Beڍ:}_ֳi;-n2iʲy12N871S5Np7ş7\S=mPm.\0!T +71!D0!@ *H !10!-10  `He0\ +7N0L0 +70 010  `He bɃMIG?iy 9xtiڶ9 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" ]N{3T}y&l5?8 O0R +7 1D0B SQL Server 2012http://www.microsoft.com/sql0  *H `!+n8Lc(6of+[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  1nƟM".us0 *H   1000^$3+b xc ցs00~0|1 0 UUS10U Washington10URedmond10U Microsoft Corporation1&0$UMicrosoft Time-Stamp PCA 2010 aN 0ZǕ. Ԥ@0  *H 3RrmG*wsW6L)IJg}n-gѺs!n׍ѢRl6T 2b, yVTj諫.`jh!-V eaߦe#7->C5Ji!Nք`bW[%igdVz}vz "x