We have a mirror MS SQL Server. We drop and re-create database snapshots on this server on every 2 hours. These snapshots are read-only because of the nature of the snapshot technology, so they can be used only for reporting, and that’s what we use them for.

Sometimes, dropping these snapshots takes a long time (such as 2.5 hours). Here’s a sample:

I wonder how and why does Ms SQL Server rollback transactions on a read-only/snapshot database! Even we assume that server is rolling back the internal transactions on tempdb, how could it take so long?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>