extended events to spy on our server between 8 and 9 am

• stan

  Ten Centuries

  Points: 1245

  More actions

  October 9, 2025 at 8:19 pm

  #4668741

  Hi, our peer who owns a remote mysql server from which we extract warehouse data daily between 8 and 9am thru ssis says there was nothing unusual nor any missing indexes this morning when querying one part of his database timed out with the error you see below.

  Our dba says it was mysql's fault.

  The query uses openquery from a linked server.    The particular query usually runs anywhere from  14 ot 23 minutes .  Today it went down after  18 minutes.    the step before it in sql agent selects a different population of data from the same db.   It usually runs in 6 minutes but took 38 minutes to finish today.

  I'm tempted to set up an extended events session to watch tomorrow between 8 and 9 am what might be interfering if its our server's fault.   But dont know if such a session can be set up in advance to only watch for an hr and be set up well in advance to do so.    I dont want to use query store because i dont think this is specific to only one db on our server.

  Can the community offer some advice?  i ran the same query into a temp table much later than that window and it ran in the usual 15 minutes successfully.