Ok, well the tempdb grew again to 37GB overnight from 35GB. As it was killing our space, we needed to restart the server. I stopped the SQL service and then...

Using this link, http://support.microsoft.com/kb/307487, method 1 looks like it used the alter db to shrink the tempdb.

But I'll give the restart the go first. Will schedule it...

Thanks. That was the solution I was leaning towards. I'm not a fan of shrinkfile either.

Ok, so that leaves one final part of the puzzle unresolved though. The fact...

Well I'm using SQL Sever 2008 R2, so if that won't work, what will work?

So I don't need to use shrink file?

So if I'm right in my understanding, I just restart the sql server service and the temp file will reduce from 35GB back...

Yes. Can't tell the exact steps that made it work but I got it working. It now points to the correct database on the new server. Nice to know that...

That's the issue. I ran the wizard again and pointed it to the correct database, but the update still tries to connect to the database I created after the original.

I...

First issue:

The Data collection is failing because it's trying to go to the new database i created and I've set it to single user mode. I have since gone back...

Well I have successfully detached, moved the database mdf and ldf files and reattached. So far so good. Now to just monitor the data collection tasks and see what happens.

Really? OK, I'll give that a go. Hopefully not too late to point it back to the existing database.

Thanks! 🙂

Thanks for the input. I've read through the article and think I'm a step closer to where I want to be.

Now, this database only has 1 table and has an...

Thanks.

I used SSMS to Shrink the transaction log file. It had 99% free and has been reduced to 1.2GB.

So... I guess my new question is, what is the best practice...

Well apparently, the transaction log backup didn't truncate the logs.

Still 35GB... Is it safe for me to now shrink transaction log with dbcc shrinkfile?

It was giving me the little red squiggly lines... but yeah, it parsed fine. Now I just have to run it. I also changed your profile and recipient parameters to...

And now it works fine again. So... I'm confused. There must be something else running on the system that was causing the issue. Nice to know that things like that...