It's technically unsupported, but you could use sp_msforeachtable to walk through and do what you want. Here's a link with examples.

Also, if you're doing restores of the databases to non-production environments, you can offload the logical consistency checks to those databases. You then can just do the physical_only checks on...

I've got several blog posts on the cost threshold for parallelism. First, we need to make sure you're on the service packs and CUs from the fall (at...

And the delete, while fast, is not free, so it's also adding a little to the time.

Getting exact measures is going to be very hard because, at the root, is the query run more than once with a unique data set each time, or a mixed...

You literally can not go wrong using Paul Randal, and his team, as a guide.

Best of luck on figuring things out. Come back here as you need...

If you're capturing query metrics on SQL Server 2012 or greater, instead of using trace, I strongly recommend you use Extended Events. It's much more lightweight and easier to filter.

Oh, and, you're on 2014. The system_health extended events session captures deadlocks. You don't need 1204. It's just going to dirty up your logs.

I honestly hate trace flag discussions.

However, I'd suggest adding 2371 to the list.