{"id":1712,"date":"2013-06-26T22:05:32","date_gmt":"2013-06-27T05:05:32","guid":{"rendered":"http:\/\/3.209.169.194\/blogs\/bobb\/?p=1712"},"modified":"2013-10-02T18:28:28","modified_gmt":"2013-10-03T01:28:28","slug":"more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/","title":{"rendered":"More XEvents in SQL Server 2014 CTP1 – don’t wait any longer"},"content":{"rendered":"

Don’t get me wrong, there’s almost no one who enjoys a good SQL Profiler diagnostic trace more than I do. But, starting in the early CTPs of SQL Server 2008, I’ve become impressed with the diagnostic enablement afforded through Extended Events. Enough to hack through that first beta (sans docs, with only metadata) and blog about it for a week<\/a>.\u00a0XEvents’\u00a0biggest weakness was that there was no GUI, and a guy named Jonathan Kehayias<\/a> took care of that\u00a0with his SSMS add-in<\/a>.<\/p>\n

In SQL Server 2012, it was announced that the old trace would be deprecated in favor of XEvents. The sheer number of events (618 in SQL Server 2012 RTM, with 9 more in SQL Server 2012 SP1) dwarfed the profiler events, as well as a nice GUI built into SSMS and programmatic interfaces for session definition, metadata, and trace-reading (including realtime) with a component called LINQ to XEvents, things were sort of sealed. That’s not even mentioning the actions, the powerful predicate system, and the series of targets.<\/p>\n

Still, XEvents seems daunting for some, mostly (I think) because there’s too much XML involved. But c’mon, XPath is, for the most part, like navigating through a file system. And basic XPath is all you need, for the most part, to reformat the event data. Goodness, the XEvent data doesn’t even use XML Namespaces, to keep the querying simple.<\/p>\n

After looking at the SQL Server 2014 CTP1 metadata, the results are in; things are settled. The score is:<\/p>\n

— 763 XEvents total (that’s 145 new ones) vs. 0 new trace events (although SQL Profiler\/event system is still around)
\n— 4 new packages, including 3 related to Hekaton (internals, compiler, and runtime).
\n— 68 events in the “sqlserver” packages, including about 10 more xtp (Hekaton) events in these packages, events to trace interactions with Windows Azure storage, for the new cardinality estimating code, and new columnstore functionality.<\/p>\n

In a release where there are actually 3 new Event Notification event types (for CREATE\/DROP AUDIT and DDL_DATABASE_AUDIT_EVENTS, remember Event Notifications?) the fact that there’s no new trace capability means YOU need to start learning\/experimenting with Extended Events now. if you haven’t already. Go to a class, or a presentation, or read blogs or something…\u00a0And\u00a0you may want to\u00a0brush up on your XPath…<\/p>\n

A good place to start would be with Jonathan’s “An XEvent A Day<\/a>” blog series. Or his two courses on Pluralsight<\/a> about them. But start NOW, before you find yourself in SQL 2012 or 2014 with your diagnostic hands tied behind your back. How else can you look at wait stats for a specific workload or work with the T-SQL stack?<\/p>\n

And BTW, Here’s a list of all the new events ([package name].[event name]) in\u00a02014 CTP1\u00a0(since 2012 SP1):<\/p>\n

hkenginexepkg.after_changestatetx_event – Fires after transaction changes state
\nhkenginexepkg.alloctx_event –
\nhkenginexepkg.attempt_committx_event – Is raised when a transaction is asked to commit
\nhkenginexepkg.before_changestatetx_event – Fires before transaction changes state
\nhkenginexepkg.compute_oldest_active_tx_hint – Indicates that the oldest active transaction hint has been recalculated
\nhkenginexepkg.dependency_acquiredtx_event – Raised after transaction takes a dependency on another transaction
\nhkenginexepkg.endts_acquiredtx_event – Fires after transaction acquires an end timestamp
\nhkenginexepkg.gc_cycle_completed – Indicates that a GC notification has been enqueued.
\nhkenginexepkg.gc_notification_enqueued – Indicates that a GC notification has been enqueued.
\nhkenginexepkg.redo_single_hk_record – Redo on a HK log record
\nhkenginexepkg.update_oldest_active_tx_stats – Indicates that an attempt is being made to recalculate the GC base generation.
\nhkenginexepkg.waiting_for_dependenciestx_event – Raised when we have explicitly waited for dependencies to clear
\nhkenginexepkg.xtp_checkpoint_file_flush – Indicates the point at which a given file has been flushed to disk.
\nhkenginexepkg.xtp_checkpoint_file_flush_complete – Indicates the point at which all in-flight buffers have been flushed to disk.
\nhkenginexepkg.xtp_checkpoint_file_read – Indicates reading of a file in XTP checkpoint recovery.
\nhkenginexepkg.xtp_checkpoint_write_io – Indicates that the checkpointing subsystem has issued or completed a write IO.
\nhkenginexepkg.xtp_create_log_record – Fires when the XTP engine creates a log record.
\nhkenginexepkg.xtp_root_file_write – Indicates that the write of the checkpoint root file is complete.
\nqds.query_store_async_shutdown_failed – Fired when query store encounters an error during async query store shutdown
\nqds.query_store_background_task_creation_failed – Fired if the background task for QDS data persistence could not be created
\nqds.query_store_background_task_initialization_failed – Fired if the background task for QDS data persistence could not be initialized
\nqds.query_store_background_task_persist_failed – Fired if the background task for QDS data persistence is not completed successfully
\nqds.query_store_begin_persist_runtime_stat – Fired immediately before current runtime statistics for a query plan is persisted to the database.
\nqds.query_store_bloom_filter_false_positive – Fired if the Bloom filter for QDS statement texts gives a false positive result
\nqds.query_store_check_consistency_init_failed – Fired when check consistency task fails during initialization
\nqds.query_store_database_initialization_failed – Fired if initialization of the Query Store for database has failed. The Query Store will be disabled for this database
\nqds.query_store_disk_size_check_failed – Fired when a check against Query Store on-disk size limit fails
\nqds.query_store_disk_size_info – Fired when a check against QDS on-disk size is performed
\nqds.query_store_execution_runtime_info – Fired when runtime information is sent to the query store.
\nqds.query_store_execution_runtime_info_discarded – Fired when runtime information sent to the query store is discarded.
\nqds.query_store_execution_runtime_info_evicted – Fired when runtime information sent to the query store is evicted.
\nqds.query_store_flush_failed – Fired when query store failed to flush dirty data
\nqds.query_store_loaded – Fired when query store is loaded
\nqds.query_store_notify_dirty_shutdown_on_partition_startup – Fired when previous instance of query store for the partition is shutdown by force in order to allow creation of a new instance
\nqds.query_store_notify_force_failure_failed – Fired when query store failed to notify force failure
\nqds.query_store_persist_task_init_failed – Fired when persist task fails during initialization
\nqds.query_store_plan_forcing_failed – Occurs when forcing of plan from qds fail
\nqds.query_store_plan_persistence_failure – Fired if there’s a failure to persist plan
\nqds.query_store_plan_removal – Fired when plan is removed
\nqds.query_store_query_persistence_failure – Fired if there’s a failure to persist query
\nqds.query_store_read_write_failed – Fired if the read\/write to Query Store internal tables failed
\nqds.query_store_statement_not_found – Fired in case when statement couldn’t be found due to race condition or ambiguous user request.
\nqds.query_store_unloaded – Fired when query store is unloaded from memory
\nsqlos.nonpreemptive_long_syncio – record long sync io operation in nonpreemptive worker
\nsqlos.stuck_dispatcher_callback_executed – Stuck dispatcher callback executed
\nsqlos.wait_completed – Occurs when there is a wait completed on a SQLOS controlled resource.\u00a0 Use this event to track wait completion.
\nsqlserver.after_natively_compiled_proc_entry_removal_on_drop – Fired after the procedure cache entry is flushed when dropping a natively compiled procedure.
\nsqlserver.before_natively_compiled_proc_entry_removal_on_drop – Fired before the procedure cache entry is flushed when dropping a natively compiled procedure.
\nsqlserver.before_redo_lsn_update – Occurs just prior to the update of the EOL LSN
\nsqlserver.buffer_pool_eviction_thresholds_recalculated – Lazywriter and\/or worker clock has wrapped the BUF array and thresholds are re-calculated.
\nsqlserver.buffer_pool_extension_pages_evicted – Page is evicted from the buffer pool extension cache.
\nsqlserver.buffer_pool_extension_pages_read – Page is read from the buffer pool extension cache.
\nsqlserver.buffer_pool_extension_pages_written – Page or contiguous set of pages evicted into the buffer pool extension cache.
\nsqlserver.check_phase_tracing – Occurs when DBCC CHECK enters a new phase of the checking. Use this event to trace the phases of DBCC CHECK process.
\nsqlserver.check_thread_message_statistics – Occurs when a phase of DBCC CHECK is finished. Use this event to collect the number of messages a DBCC CHECK thread has sent or received.
\nsqlserver.check_thread_page_io_statistics – Occurs when a phase of DBCC CHECK is finished. Use this event to collect the number of logical, physical, and read-ahead IOs a DBCC CHECK thread has performed.
\nsqlserver.check_thread_page_latch_statistics – Occurs when a phase of DBCC CHECK is finished. Use This event to collect the number and time of page latch and IO latch waits.
\nsqlserver.clustered_columnstore_index_rebuild – Occurs when clustered index on the table was rebuilt. This event is raised three times for ALTER index rebuild operation on CCSI. The event is raised when the operation takes lock on index rebuild resource, when lock is taken on the table and when S lock on the table is upgraded to SCH_M lock to switch indexes in metadata.
\nsqlserver.column_store_index_build_low_memory – Occurs when Storage Engine detects low memory condition and the rowgroup size is reduced.
\nsqlserver.column_store_index_build_process_segment – Occurs when a segment is processed
\nsqlserver.column_store_index_build_throttle – Shows the statistics of columnstore index build parallelism throttling
\nsqlserver.columnstore_tuple_mover_begin_compress – Occurs when column store tuple mover starts compressing a deltastore.
\nsqlserver.columnstore_tuple_mover_end_compress – Occurs when column store tuple mover is done compressing a deltastore.
\nsqlserver.database_xml_deadlock_report – Produces a deadlock report for a victim, with information scoped to the victim’s database.
\nsqlserver.db_lock_acquired_from_cache – Occurs when a DB lock is acquired from the XactWorkspace DB lock cache.
\nsqlserver.db_lock_released_from_cache – Occurs when a DB lock is released from the XactWorkspace DB lock cache.
\nsqlserver.ddl_with_wait_at_low_priority – A DDL statement was executed using the WAIT_AT_LOW_PRIORITY options
\nsqlserver.diag_quantum_end – Occurs when the diag is notified of quantum end.
\nsqlserver.dyn_throttle_checkpoint – Occurs when checkpointing has been dynamically throttled with a new Checkpoint rate.
\nsqlserver.feature_extension – Occurs when received and parses data for a feature in feature extension.
\nsqlserver.file_read_enqueued – File read enqueued
\nsqlserver.file_read_throttled – File read throttled
\nsqlserver.file_write_enqueued – File write enqueued
\nsqlserver.file_write_throttled – File write throttled
\nsqlserver.hadr_tds_synchronizer_payload_skip – Hadron Tds Listener Synchronizer skipped a listener payload because there were no changes since the previous payload.
\nsqlserver.lock_request_priority_state – The priority state of a lock request
\nsqlserver.log_cache_write_block – Writing a log block to the log cache
\nsqlserver.logreader_start_scan – Outputs the replnextlsn value from the database table that the first replcmds scan uses as a starting point.
\nsqlserver.metadata_ddl_add_column – Occurs when an ALTER TABLE ADD column operation is updating base index.
\nsqlserver.metadata_ddl_alter_column – Occurs when an ALTER TABLE ALTER column operation is updating base index.
\nsqlserver.metadata_ddl_drop_column – Occurs when an ALTER TABLE DROP column operation is updating base index.
\nsqlserver.mixed_extent_activation – Track mixed extent activation and deactivation operations.
\nsqlserver.mixed_extent_allocation – Track mixed extent allocation operations
\nsqlserver.mixed_extent_deallocation – Track mixed extent deallocation operations.
\nsqlserver.mixed_page_allocation – Track mixed page allocation operations
\nsqlserver.mixed_page_deallocation – Track mixed page allocation operations
\nsqlserver.mixed_page_scan_file – Track the activity of SGAM scans for mixed page allocation
\nsqlserver.mixed_page_scan_page – Track the activity of SGAM scans for mixed page allocation
\nsqlserver.mixed_page_skipextent – Track the activity of SGAM scans for mixed page allocation
\nsqlserver.natively_compiled_proc_execution_started – Fired before a natively compiled procedure is executed.
\nsqlserver.optimizer_timeout – Occurs when the optimizer times out either due to spending too much time or hitting a memory limit.\u00a0 Use this event to look at all the queries that are impacted by the optimizer timeout in a particular workload. This can be very useful when tuning a particular workload.
\nsqlserver.plan_affecting_convert – Occurs when a type convert issue affects the plan.\u00a0 The expression value indicates the conversion that can cause inaccurate Cardinality Estimation or prevent from using a seek based plan in the query plan choice.\u00a0 If performance is affected, rewriting the query could help.
\nsqlserver.process_killed_by_abort_blockers – A process is killed by an ABORT = BLOCKERS DDL statement
\nsqlserver.query_execution_batch_hash_aggregation_finished – Occurs at the end of batch hash aggregation.
\nsqlserver.query_execution_batch_hash_children_reversed – Occurs each time when hash join reverses build and probe side while processing data spilled to disk.
\nsqlserver.query_execution_batch_hash_join_spilled – Occurs each time when hash join spills some data to disk in batch processing.
\nsqlserver.query_optimizer_estimate_cardinality – Occurs when the query optimizer estimates cardinality on a relational expression.
\nsqlserver.query_optimizer_force_both_cardinality_estimation_behaviors – Both traceflags 2312 and 9481 were enabled, attempting to force both old and new cardinality estimation behaviors at the same time. The traceflags were ignored. Disable one or both of the traceflags.
\nsqlserver.query_store_failed_to_capture_query – Fired if the Query Store failed to capture query. The Query Store will not track statistics for this query
\nsqlserver.query_store_failed_to_load_forced_plan – Fired if the query failed to load forced plan from QDS. Forcing policy will not be applied
\nsqlserver.query_store_persist_on_shutdown_failed – Occurs when SQL Server fails to store dirty entries in Query Store on database shutdown.
\nsqlserver.selective_xml_index_no_compatible_sql_type – Occurs when a value() method is used in a query, specifying a sql type that differs from the type specified during selective XML index creation for that path.
\nsqlserver.selective_xml_index_no_compatible_xsd_types – Occurs when the user specifies a different resulting XSD type in a query, than the one that was used to promote the path during selective XML index creation.
\nsqlserver.selective_xml_index_path_not_indexed – Occurs when the path given in the user query is not promoted in the selective XML index, and thus the index is not used.
\nsqlserver.selective_xml_index_path_not_supported – Occurs when selective XML index is not used for a XML query due to the user using an unsupported path type.
\nsqlserver.session_recoverable_state_change – Occurs when the server determines a state change in term of session recovery on a connectionresilency-enabled connection.
\nsqlserver.spatial_guess – Occurs when the optimizer cannot get enough join selectivity information.\u00a0 Use this event to look at the queries where spatial index could be used and the optimizer guesses the spatial selectivity.
\nsqlserver.unmatched_filtered_indexes – Occurs when the optimizer cannot use a filtered index due to parameterization.\u00a0 For each such index an event is fired.\u00a0 The unmatched_database_name, unmatched_schema_name, unmatched_table_name, unmatched_index_name fields give details of the filtered index that could not be used.
\nsqlserver.xfcb_blob_properties_obtained – Windows Azure Storage blob property is obtained from response header.
\nsqlserver.xfcb_failed_request – Failed to complete a request to Windows Azure Storage.
\nsqlserver.xfcb_header_obtained – Response header is obtained from request to Windows Azure Storage.
\nsqlserver.xfcb_read_complete – Read complete from Windows Azure Storage response.
\nsqlserver.xfcb_request_opened – A request is opened to Windows Azure Storage.
\nsqlserver.xfcb_send_complete – Request send to Windows Azure Storage is complete.
\nsqlserver.xfcb_write_complete – Request send to Windows Azure Storage is complete.
\nsqlserver.xtp_create_procedure – Occurs at start of XTP procedure creation.
\nsqlserver.xtp_create_table – Occurs at start of XTP table creation.
\nsqlserver.xtp_deploy_done – Occurs at completion of XTP object deployment.
\nsqlserver.xtp_matgen – Occurs at start of MAT generation.
\nsqlserver.xtp_offline_checkpoint_scan_start – Fired by XTP offline checkpoint when the checkpoint thread begins.
\nsqlserver.xtp_offline_checkpoint_scan_stop – Fired by XTP offline checkpoint when the checkpoint thread stops.
\nsqlserver.xtp_recover_done – Occurs at completion of log recovery of XTP table.
\nsqlserver.xtp_recover_table – Occurs at start of log recovery of XTP table.
\nsqlserver.xtp_storage_table_create – Occurs at just before the XTP storage table is created.
\nucs.ucs_connection_rejected_by_proxy_whitelist – After a connection attempt to the UCS proxy endpoint is rejected by whitelist check
\nucs.ucs_proxy_connect_next_hop – UCS proxy next hop connection
\nucs.ucs_proxy_receive_proxy_connect_message – UCS proxy receive proxy connect message
\nucs.ucs_proxy_route_add – UCS proxy route added
\nucs.ucs_proxy_route_disable – UCS proxy route disabled
\nucs.ucs_proxy_route_refresh – UCS proxy route refreshed
\nucs.ucs_proxy_send_proxy_connect_message – UCS proxy send proxy connect message
\nXeXtpCompilePkg.cgen – Occurs at start of C code generation.
\nXeXtpCompilePkg.invoke_cl – Occurs prior to the invocation of the C compiler.
\nXeXtpCompilePkg.mat_export – Occurs at start of MAT export.
\nXeXtpCompilePkg.pit_export – Occurs at start of PIT export.
\nXeXtpCompilePkg.pitgen_procs – Occurs at start of PIT generation for procedures.
\nXeXtpCompilePkg.pitgen_tables – Occurs at start of PIT generation for tables.
\nXeXtpRuntimePkg.bind_md – Occurs prior to binding metadata for a memory optimized table.
\nXeXtpRuntimePkg.bind_tables – Occurs prior to binding tables for a natively compiled procedure.
\nXeXtpRuntimePkg.create_table – Occurs prior to creating memory optimized table.
\nXeXtpRuntimePkg.deserialize_md – Occurs prior to deserializing metadata.
\nXeXtpRuntimePkg.load_dll – Occurs prior to loading the generated DLL.
\nXeXtpRuntimePkg.recover_done – Occurs at completion of checkpoint recovery of a memory optimized table.
\nXeXtpRuntimePkg.recover_table – Occurs at start of checkpoint recovery of a memory optimized table.
\nXeXtpRuntimePkg.serialize_md – Occurs prior to serializing metadata.<\/p>\n

Enjoy.<\/p>\n

Cheers, Bob<\/p>\n","protected":false},"excerpt":{"rendered":"

Don’t get me wrong, there’s almost no one who enjoys a good SQL Profiler diagnostic trace more than I do. But, starting in the early CTPs of SQL Server 2008, I’ve become impressed with the diagnostic enablement afforded through Extended Events. Enough to hack through that first beta (sans docs, with only metadata) and blog […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,42,41],"tags":[],"class_list":["post-1712","post","type-post","status-publish","format-standard","hentry","category-event-notifications","category-hekaton","category-sql-server-2014"],"yoast_head":"\nMore XEvents in SQL Server 2014 CTP1 - don't wait any longer - Bob Beauchemin<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"More XEvents in SQL Server 2014 CTP1 - don't wait any longer - Bob Beauchemin\" \/>\n<meta property=\"og:description\" content=\"Don’t get me wrong, there’s almost no one who enjoys a good SQL Profiler diagnostic trace more than I do. But, starting in the early CTPs of SQL Server 2008, I’ve become impressed with the diagnostic enablement afforded through Extended Events. Enough to hack through that first beta (sans docs, with only metadata) and blog […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/\" \/>\n<meta property=\"og:site_name\" content=\"Bob Beauchemin\" \/>\n<meta property=\"article:published_time\" content=\"2013-06-27T05:05:32+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2013-10-03T01:28:28+00:00\" \/>\n<meta name=\"author\" content=\"Bob Beauchemin\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Bob Beauchemin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"15 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/\",\"name\":\"More XEvents in SQL Server 2014 CTP1 - don't wait any longer - Bob Beauchemin\",\"isPartOf\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/#website\"},\"datePublished\":\"2013-06-27T05:05:32+00:00\",\"dateModified\":\"2013-10-03T01:28:28+00:00\",\"author\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/#\/schema\/person\/62bfa986c5b5d28fcffd8b4fc409c73e\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Event Notifications\",\"item\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/category\/event-notifications\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"More XEvents in SQL Server 2014 CTP1 – don’t wait any longer\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/#website\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/\",\"name\":\"Bob Beauchemin\",\"description\":\"SQL Server Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/#\/schema\/person\/62bfa986c5b5d28fcffd8b4fc409c73e\",\"name\":\"Bob Beauchemin\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/6f80e6cc667410857fa6a21931dc528b8092f4d112bf7a8ff7c267674d44ee37?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/6f80e6cc667410857fa6a21931dc528b8092f4d112bf7a8ff7c267674d44ee37?s=96&d=mm&r=g\",\"caption\":\"Bob Beauchemin\"},\"sameAs\":[\"http:\/www.sqlskills.com\/blogs\/bobb\/\"],\"url\":\"https:\/\/www.sqlskills.com\/blogs\/bobb\/author\/bobb\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"More XEvents in SQL Server 2014 CTP1 - don't wait any longer - Bob Beauchemin","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/","og_locale":"en_US","og_type":"article","og_title":"More XEvents in SQL Server 2014 CTP1 - don't wait any longer - Bob Beauchemin","og_description":"Don’t get me wrong, there’s almost no one who enjoys a good SQL Profiler diagnostic trace more than I do. But, starting in the early CTPs of SQL Server 2008, I’ve become impressed with the diagnostic enablement afforded through Extended Events. Enough to hack through that first beta (sans docs, with only metadata) and blog […]","og_url":"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/","og_site_name":"Bob Beauchemin","article_published_time":"2013-06-27T05:05:32+00:00","article_modified_time":"2013-10-03T01:28:28+00:00","author":"Bob Beauchemin","twitter_misc":{"Written by":"Bob Beauchemin","Est. reading time":"15 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/","url":"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/","name":"More XEvents in SQL Server 2014 CTP1 - don't wait any longer - Bob Beauchemin","isPartOf":{"@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/#website"},"datePublished":"2013-06-27T05:05:32+00:00","dateModified":"2013-10-03T01:28:28+00:00","author":{"@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/#\/schema\/person\/62bfa986c5b5d28fcffd8b4fc409c73e"},"breadcrumb":{"@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/more-xevents-in-sql-server-2014-ctp1-dont-wait-any-longer\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.sqlskills.com\/blogs\/bobb\/"},{"@type":"ListItem","position":2,"name":"Event Notifications","item":"https:\/\/www.sqlskills.com\/blogs\/bobb\/category\/event-notifications\/"},{"@type":"ListItem","position":3,"name":"More XEvents in SQL Server 2014 CTP1 – don’t wait any longer"}]},{"@type":"WebSite","@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/#website","url":"https:\/\/www.sqlskills.com\/blogs\/bobb\/","name":"Bob Beauchemin","description":"SQL Server Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.sqlskills.com\/blogs\/bobb\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/#\/schema\/person\/62bfa986c5b5d28fcffd8b4fc409c73e","name":"Bob Beauchemin","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqlskills.com\/blogs\/bobb\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/6f80e6cc667410857fa6a21931dc528b8092f4d112bf7a8ff7c267674d44ee37?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6f80e6cc667410857fa6a21931dc528b8092f4d112bf7a8ff7c267674d44ee37?s=96&d=mm&r=g","caption":"Bob Beauchemin"},"sameAs":["http:\/www.sqlskills.com\/blogs\/bobb\/"],"url":"https:\/\/www.sqlskills.com\/blogs\/bobb\/author\/bobb\/"}]}},"_links":{"self":[{"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/posts\/1712","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/comments?post=1712"}],"version-history":[{"count":0,"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/posts\/1712\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/media?parent=1712"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/categories?post=1712"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/bobb\/wp-json\/wp\/v2\/tags?post=1712"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}