Actually a little shocked I got it right.

I was thinking more about hardware style solutions. Pure Storage has an internal snapshot mechanism that is fully transactionally aware. It would be worth pursuing, depending on your functional needs....

First, AlwaysOn is marketing speak. You want to talk about Availability Groups. That's the technical implementation that you'll be working with. Just knowing that will help all your web searches,...

If the database is sitting there, not being accessed, not being connected to, zero activity, nah, it's not hurting performance. It can't. It will affect storage of course, but again,...

In 2016 Sp2(?) or greater, that just means parallelism is occurring. What else?

If it's SQL Server, it has to be a query. Something has to be running there. Otherwise, it might not be SQL Server. However, I'd go with the Extended Events...

Nah thought I had one but no luck retrieving it.

I get better luck when...

Honestly, I thought we had pulled this from the product, but I was wrong. Here you go, object level recovery in Redgate SQL Backup.

Yes, I am replacing TRUNCATE with DELETE.  There are around 150 tables in total & for around 80 tables I have to reset the identity. Rest, of the...

Availability Groups will be an easier solution I'd think. Replication is just a big ball of trouble, without going into the fact that they have tables without primary keys (<sigh>)....

If it's SQL Server, then it's caused by queries. So, go and look at query behavior. There are three ways to do this, in order to accuracy and detail: DMVs...

In SSMS go to the first operator in the plan. Right click it. Select "Properties" from the list. A tab will open on the side. Pin that in place by...

What about using extended events to look for specific queries successfully completing?

Sure. Just not straight forward. On SQL Server 2014, you have really two good options. One will give you a general understanding of the behavior. The other will give you...

You're going to need more and deeper information here. CXCONSUMER is a standard wait that simply means parallelism is occurring. It's not in any way actionable. You can read