November 8, 2007 at 9:15 am
Hi,
This morning our tempdb size shot up and filled up our drive. It went from around 2 gigs to 24 gigs. We failed over since we had to be back up. How can we monitor this kind of activity.
Sam
November 8, 2007 at 9:41 am
Hey,
I would suggest you set-up an alert in performance monitor to send an email, when data file size for tempdb is over a comfortable threshold, which provides ample opportunity for you to resolve before growth consumes all your drive space.
You can use the Perfmon counter SQL Server Databases: Data File Size to achive such an alert.
Thanks,
Phillip Cox
November 8, 2007 at 9:45 am
I'd do what Phillip suggested and also you might want to ensure there are limits to how tempdb can grow. If you allow autogrow, you might set a "space holder" on the drive, a large 1GB or so file that sits there and you can delete if need be in an emergency.
November 8, 2007 at 11:26 am
Heh... sounds to me like someone wrote an accidental Cartesian join and decided to wait for it to complete...
--Jeff Moden
Change is inevitable... Change for the better is not.
November 8, 2007 at 11:59 am
We acutally found a reporting services query that was running against oracle and was pulling two tables - one with 15 rows, one with 500k. No joins...that was last weeks bonehead query.
Now this!
I've created the alert (which was a very good thing for me to do - I didn't know you could use performance counters in there!!!!). Need to do some research on what to do once we know it is happening. I assume there is probably some info out there on how to do it, so I'll get to it.
Thanks alot!
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply