The only two things that change...

Yes.

ALTER TABLE <table name> ADD <column name> BIT NOT NULL DEFAULT 0;

A failover involved SQL starting cold on the second node. There's no memory transfer, the databases are shared but that's all.

Restart the instance, it's a hung rollback. If it's 0 seconds remaining, there won't be a prolonged recovery period.

Recovery models have no effect on rollback, so doesn't matter which one...

Cool. In that case the business rules for how, when and by what criteria rows are archived will guide your choice of partition column.

sqlguy-736318 (3/13/2013)

---

"If you have no indexes, that's a table scan and SQL will apply both filters as it scans the table."

Gail - Correct me if I'm wrong but if I...

The TOP has very little to...

What are you trying to achieve by partitioning?

Depends on the indexes you have.

If you have no indexes, that's a table scan and SQL will apply both filters as it scans the table. If you have an...

Encouraging copyright violation there are we.... I hope you're not also telling people to steal books that I've written, I get little enough royalties...

Why are you partitioning? What's the goal here?

Restore from last good backup, that's irrepairable.

If there's absolutely no backup whatsoever, export all the documents, lists, etc from sharepoint (not a SQL data export), then drop and recreate the...

Exactly the same as a join between two normal tables. Yes, your example is completely correct.

Ignore it? If it's not causing any problems, just ignore it.

Oh, and don't shrink TempDB, it's documented to be able to cause corruption.

There's no such list. The optimiser can pick table scans even when the where clause looks like it could use an index. Has to do with % of rows returned,...