You should have to provide the schema. It prevents issues with naming collisions.

I can't remember if this worked in 2005 for me, but in 2008 and R2, this hasn't worked...

The question was poorly worded and I missed the total disk activity in edit.

The question has been corrected and points awarded back as of a few minutes ago.

Seems strange. Can you check/post the execution plan in both cases?

Closing this as it has gotten out of hand.

If you disagree with an answer, please feel free to disagree without using insults or name calling. This is a professional forum...

Can someone let me know when Steve Smith is planning on showing up this year? I'll add him back to me line up then.

I'm not sure there's a stairway here, but we'll debate it. The stairways were designed to get you up to speed on certain SQL Server technologies. This is near the...

Users working with data don't impact the data reading portion of the backup. They can impact the log, as noted above, but that's mostly depending on the amount of logging...

There might be something in Windows, but I'm not familiar enough to know what you'd have to check. Someone or something (patch, SP) might have altered the dependency somehow. Or...

Everyone is possibly not...

You might read this: http://msdn.microsoft.com/en-us/library/cc949109.aspx

If the files are small (250kb or less, stick them in the db.

If they are larger, >1MB, use the filesystem.

A separate database is a good idea,...

You might also read this: http://www.sqlservercentral.com/articles/SQL+Server+2008/65292/

I tend to look for personality and ambition. You have to fit in with the group, and work as a team. Ambition/motivation is important since it means you can/will learn...

Ditto, I was hoping the Pirates would stay in it.

Nail biting time in the AL, NL looks fairly settled barring a big collapse.

Nice to see the As in there at the end. Go Moneyball!

Grant Fritchey (9/19/2012)

---

Nothing wrong with this maintenance plan. I mean, everything is covered:

1. Check DB Integrity

2. Back Up Db Full

3. Back up Db transaction log

4. Shrink Db

5. Rebuild index

6. Update...