He's trying to fail database mirroring over to the mirror after the principal crashed.

From Books Online:

FORCE_SERVICE_ALLOW_DATA_LOSS

Forces database service to the mirror database after the principal server fails with the database in an unsynchronized state or in a synchronized state when automatic failover does...

So the DB is online and working?

None whatsoever

Wouldn't the WITH(NOLOCK) defeat the whole purpose of discouraging against...

D.Post (11/22/2012)

---

Sorry skipped straight to my 2cents. (Nearly time to go home :-))

Maybe this has already been pointed out and I'm just proving the point of many comments already raised...

Should be OK because ROWLOCK is not an isolation level hint, it's a lock granularity hint. It says 'when you take locks, take at the row level not page or...

See my earlier post. You have an index rebuild job that is rebuilding every single index in your database every time it runs.

Has the DB just been switched from full or bulk-logged recovery? If so, run a checkpoint, sys.databases is not updated immediately, hence you can get 'log backup' occurring for a...

No, it's part of the SQL Server installation. Run the SQL Server installation on their machine and just select...

Please post the actual complete procedure, table definitions, index definitions and execution plan, as per http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

It's probably the hidden database snapshot that CheckDB uses.

There is something running a second backup job on that server. The LSNs and times are different, hence it is not the same backup being logged twice. VDI means it's...

josh.hill (11/21/2012)

---

A successful simple maint plan will consume between 40% and 80% of the trans log. A failure will max out the log. What other pieces of...

The ones you aren't...

No, not conclusively.

You can check the index usage stats for a DB, if there's nothing in there then the DB hasn't been used since the last time the server was...