No worries. I think it was handled very well and have to admit I had a good laugh about it.

What a strange, strange... strange thing to do. :laugh:

Thanks...

Here's a link to the plagiarized version

enjoy.

They're probably disabling the indexes, then re-enabling and rebuilding them.

Not uncommon and a good way to go.

I'm guessing they are missing that one in their load script.

~BOT

Lee Sloan (1/13/2009)

---

Hmmm... that sounds suspiciously like we need to cover...

I don't think there would be much difference, as behind the scenes you essentially have a lock, logged page deallocation, and index build + logging in both cases.

Best way is...

The way I usually do things is to try to check return codes and handle the error at the procedure level...

I code all my stored procs to return specific codes...

george sibbald (1/12/2009)

---

SQLBOT (1/12/2009)

---

Andy Steinke (1/12/2009)

---

Your organization needs to suppoort saying no; it's easy to say this from an ivory tower perspective but you have to have management and executive...

This is very...

Jonathan Kehayias (1/8/2009)

---

SQLBOT (1/8/2009)

---

I think it depends on your rationale.

Normally I go for a single host\instance for the performance. The reason we use virtualization is for vended applications that...

Great idea, great Article. Keep 'em coming!

5 stars!!

~BOT

I'm pretty sure this is a negative result of parallelism.

I think setting your server-level MAXDOP to 0 means that you're letting SQL Server manage it instead of specifying a value....

I've never heard that, so of course I googled around...

If you trust this SQL Server Magazine, this guy says only Developer's Ed. and EE support asynchronous.

http://www.sqlmag.com/Article/ArticleID/47129/sql_server_47129.html

We only have EE, so...

Oh yeah...

it took me a minute to find it. But I like where it is in 2008 better.

I don't like the fact that the lock information is missing, because...

Also, the fragmentation percent depends on the order with which the data is inserted related to the index order...

http://www.sqlservercentral.com/articles/Index+fragmentation/64424/%5B/url%5D

so fill factor isn't always the answer!

~BOT

High sometimes means above your baseline.

sometimes it is a concrete number... sometimes (like this one) it's calculus.

for Fill factor, the level of index fragmentation and how quickly it gets fragmented...