Likely causes for increased size in your tempdb are:

Poorly written SQL that uses tempdb heavily. Transaction is probably still ongoing.

Index rebuilds

The most likely cause is the Poorly written SQL....

GilaMonster (1/25/2010)

---

Absolutely. Comma-delimited lists in a column are a violation of 1st Normal Form and...

You're welcome. Glad to be of assistance.

Here is a nice resource for your questions

http://www.doubletake.com/ENGLISH/RESOURCES/Pages/default.aspx

Couldn't help myself on that one. Let's see if the OP can go and figure it out now.

Here is a thread that may help you find your solution. You will still need to look at the code and determine how to adapt it to your situation....

Welcome back. Hope it was restful,...

tweet tweet

Good statistics will help improve query performance.

The downside is that you will need to perform maintenance on those indexes - which you should be doing anyway. If you don't...

you're welcome

You can use those scripts in production - but only do so after you have tested, tested, and tested some more.

Some of the recommendations from DTA are good. Not...

It does not run in the background per se. The maint plan should be executing the same script and taxing your server just the same as if you ran...

It looks like you might have a corrupted registry string.

Check the following:

http://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/72afb885-c158-4508-bfd2-61f3a877a940

If the copy job is truly failing, then it shouldn't be able to restore and be in synch.

Are you copying to multiple locations by chance?

Alvin Ramard (1/23/2010)

---

WayneS (1/23/2010)

---

Well, USPS just delivered my "SQL SERVER MVP Deep Dives". After a quick scan through it, all I can say is WOW! All these MVPs did a...