Thanks, I actually was able to test this, and indeed the times reflect the completion of the query. Mystery solved!

In SQL 2016 both clustered and non-clustered columnstore indexes are updateable, so there is no need to disable them prior to updates to the underlying table:

Columnstore Indexes Versioned Feature Summary

Thanks...

Enjoyed the scripts and explanations.

Nice article, thank you!

Great post. It brings to mind many such situations that I have experienced in the past.

I think what exacerbates these situations is the "urgency" of the project - a looming...

A better way of terminating all Service-Broker activity in a given database:

ALTER DATABASE [dbName] SET NEW_BROKER WITH ROLLBACK IMMEDIATE;

See:

http://stackoverflow.com/questions/22392341/alter-database-db-name-set-enable-broker-with-rollback-immediate

http://stackoverflow.com/questions/6931001/how-to-quickly-shut-down-all-elements-of-microsoft-sql-server-service-broker

Thank you, I should've thought of that - I'll check.

Here is a query that will give output to help kill broker-activated tasks:

SELECT

'KILL ' + cast (at.spid as varchar)

, ...

david.puckett 38841 (7/25/2014)

---

3 node windows 2012 failover cluster

sql2012 installed on node 1 and node 2

node 1 and node 2 -> instance 1 using V: on san as clustered storage

from node...

Thanks, I'll schedule a live session with SQL Sentry to get set up to better be able to capture these.

Perhaps this link has the answer:

https://www.simple-talk.com/sql/database-administration/investigating-transactions-using-dynamic-management-objects/

Thank you, I know about sp_whoisactive, and I have used it in the past.

To be honest, I think this is more of a limitation of what info current DMVs (in...

Thank you all!

D-SQL (5/20/2014)

---

This is great, I am new to service broker and wanted to get some questions answered. I set this up and was trying to configure it to run on...

No, we saw some of these on April 14, last weekend.

They coincide with a sql-agent service shutdown and restart.

Perhaps some jobs were not stopped cleanly during the shutdown and that...

Hmm, mostly habit I guess...

I've removed them, so they do not detract from the "real" issue.