Thanks for all answers received. I have investigated further and it appears we're running into multiple regressed queries throughout the workload:

I've been reluctant to enable the...

It turns out the virtual store is being used up by a trigger.

There's a nice explanation here: https://www.itprotoday.com/sql-server/triggers-and-version-store

My other mystery is why the virtual store space isn't necessarily...

Availability groups are not enabled on the server. Thanks.

snapshot_isolation_state = 0 for all the databases listed above.

All worked successfully.

OK. Thanks for all the responses. We'll be doing this a couple times in next few weeks and if we have any issues, I'll report back.

Makes sense. I think the log shipping restore job inspects each file to see whether it has LSNs to be restored...scanning all those files would take a long time I...

No, we never did find a solution other than switching to "no recovery mode" and then back to standby once it was caught up or just backing up the source...

Add @append_query_error = 1 to the call to sp_send_dbmail

That way an email will be sent with the results of the attempt to run the query.

It's running at normal priority...I did try setting it to high but it didn't make any difference.

I've got the contents of the restorehistory records for the .trn file listed below...I tried to format it but I couldn't get a nice display to work in using this...

2011-04-26 19:13:13.18 Backup Log was restored. Database: QAI, creation date(time): 2008/02/12(11:37:56), first LSN: 24837:114963:1, last LSN: 24922:13456:1, number of dump devices: 1, device information: (FILE=1,...

Thanks for the response.

There are 147 VLFs. I checked at the time and 147 didn't seem like too many. It's the same number on both the fast and slow server...

Spoke too soon. I was calling procedures from the main procedure that would output the result set. The only way I could get rid of the errors was to break...

A bit late maybe...

I had a similar problem caused by a sproc parameter declared as a VARCHAR(MAX). Changing MAX to 20 stopped the error.