February 26, 2015 at 4:47 pm
Make sense that tempDB can/should grow from time to time but what I witnessed today confused me.
We have DB (size around 16 GB) in Staging env where vendor application loaded data to from Oracle.
Not sure how much data was loaded (certainly less than 1 GB) but during load process tempDB simply exploded and reached 42 GB in size. I checked what occupies space (sys.dm_db_file_space_usage ) and found- it’s all about Internal objects (internal_object_reserved_page_count) . As per MS it can be “cursor work tables, LOBs, hash joins or sorts”. But still it’s not clear- where this huge 42GB coming from? After load process completed- 41GB marked as empty. Any experience from the past or hint is really appreciated. Thanks
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply