Add an Extended Events action for query_id
When you are investigating a performance problem it is useful to be able to go from Extended Events to Query Store. Let's say that you have collected data from events like spstatementcompleted, sqlstatementcompleted, and wait_completed, and now you want to look at query plans in Query Store.
The first step when using Query Store is to find the queryid. You can use tsqlframe (handle, offsetStart and offsetEnd) and the queryhash in Extended Events, but you also need the contextsettings_id (not available in Extended Events).
Wouldn't it be possible to add an action for query_id in Extended Events? That would make it easy to go from Extended Events to Query Store.
Upvotes: 3<=-=May 27 2017 9:54AM=-=>
Thank you for taking the time to post this issue! We understand that this could be an important issue for you.
Unfortunately, we do not plan to include a fix for this issue in the upcoming release, although, we might include it as an improvement in a future release.