Yes, that's database mirroring. No, it would not have caused the backup error. It's likely to cause you lots more fun unless you resume the mirroring or remove the mirroring...

Since repair allow data loss is the minimum repair level necessary, running checkDB with...

The general recommendation when splitting ranges is to ensure that no existing data will have to move to a new partition. If it does, trhen you get what you saw,...

No, Task manager gives exact values, not estimated. It can be wrong because it doesn't count memory allocated via the...

Not a picture of the exec plan, which is fairly useless. The execution plan saved to a file. Plus the view definition, the table definitions, the index definitions.

Please read the...

Index maintenance whenever you have time. Integrity checks probably before the backup. It's nice to know whether the DB is corrupt or not before backing it up.

The source database is probably damaged. Discard that backup, it's likely to be fairly useless. You shouldn't be worrying about the backup at this point, worry about the DB that...

Those two should be scheduled based on your backup strategy and your SLAs.

You also need integrity checks and index maintenance at a minimum.

SQL Monitor does not defragment the DB and all...

If you're not going to analyse it (in a debugger) or send it to product support, delete it.

Heaps?

Autoshrink or manual shrink?

Partitioning is not primarily for performance, it's primarily for maintainability.

https://www.simple-talk.com/sql/database-administration/gail-shaws-sql-server-howlers/

There's no such term or feature in SQL Server as 'materialised view log'. A brief google search shows it's an Oracle feature.

What are you trying to achieve here?

rocky_498 (11/30/2012)

---

Gila I am 100% agree with you, Due to time issue it is really hard for us to go that path, Yes for feature we have to use that...

Blocking, waits, different execution plan (due to different set options), etc