Every now and then you get a helpful alert from one of your database servers about disk space being low (you're monitoring that, right?), or a bunch of autogrowth alerts (you're monitoring that too, right?) - but what happens when you get these for a database that you don't expect growth in? Further, what happens when that database is growing rampantly (say like 1GB/hr in my case) and it's a canned database from a 3rd party product? This time it was the database that SolarWinds uses for collection - and apparently it was collecting a lot of something that it wasn't collecting before.
- you send out an email asking the end users of the system (IT in this case) if anything changed
- adjust so said system stops trying to fill up your drives
Unfortunately, there's often quite a few possibilities for "why" a database is growing - and when it's a canned product, you don't always have the best understanding of why it does what it does when it does it. As a Database Admin, you can help diagnose the problem by letting everyone know what exactly is growing:
SELECT DirName, LeafName, tp_Email, CheckoutDate, IsCheckoutToLocal FROM AllDocs d WITH(nolock) INNER JOIN Webs w WITH(nolock) ON d.WebId = w.Id INNER JOIN Sites s WITH(nolock) ON w.SiteId = s.Id INNER JOIN UserInfo u WITH(nolock) ON (s.Id=u.tp_SiteID AND u.tp_ID=CheckoutUserId) WHERE d.Type <> 1 AND (LeafName LIKE '%.xls' OR LeafName LIKE '%.xlsx') AND (LeafName NOT LIKE '%template%') AND DeleteTRansactionId = CAST(0 AS VARBINARY) AND IsCurrentVersion = 1 AND IsCheckoutToLocal = 1 ORDER BY tp_Email ASC