Wait, or drop it and restore from your last backups.

Or maybe call MS support and get someone on site if your agreements with them allow. Will cost. They might be...

It'll be removed when ghost cleanup runs. It's done this way as an optimisation, SQL is cleaning up space properly, no it will not slow down inserts.

Why are you casting to Varchar? It's just going to force SQL to convert back to date, that's expensive conversions.

~0.5%, unless the index is covering (which a clustered index always is), in which case anything...

Are you explicitly inserting NEWID() into the table, or are you allowing the default to be used?

Post your questions in the relevant administration forum. PBM is a nice feature, but it's too specific to have a forum just for it. Hell, we've got way too many...

Nothing will happen to the existing values. If the table is fragmented before you change the default, rebuild your indexes.

Is the maintenance plan doing compressed backups?

Is the maintenance plan doing differential backups?

Is the maintenance plan striping the backup over multiple files?

WayneS (5/21/2014)

---

TomThomson (5/20/2014)

---

Steve Jones - SSC Editor (5/20/2014)

---

Who's getting a Surface 3? Or wants one?

Up in the air on this whole thing, but I'll admit it's tempting, depending on price....

It's perfectly safe to kill anything (well, unless your developers have written procedures which don't use transactions, but that's not a SQL internals problem)

That's not a quick explanation, that's a chapter. Specifically, it's a chapter in SQL Server 2005 Practical Troubleshooting (http://www.amazon.com/SQL-Server-2005-Practical-Troubleshooting/dp/0321447743/)

No.

http://www.sqlskills.com/blogs/paul/checkdb-from-every-angle-consistency-checking-options-for-a-vldb/

The CheckDB operation stops.