January 28, 2014 at 3:47 pm
I have an SSIS package, running from a dedicated ETL server, that sucks data from our source system over to a staging database in the data warehouse. Recently, our DBA started noticing that the TEMPDB on the source system was ballooning out overnight while the SSIS packages were running.
I've tried to diagnose the cause of the issue. But most google results are about the TEMPDB on the ETL server, or the destination... not the source system. Most of the tables are copied from the source system using the Object Transfer module. But in response to the issue, I moved some of the largest tables to use Data Flow Tasks (I was worred the Object Transfer might be causing some kind of unexpected issue). But it hasn't resolved anything.
To put the problem in perspective, the total size of the staging area in our data warehouse is about 30GB. But during transfers, the tempdb in our source system is growing to 80GB.
Can anyone provide any help on how to diagnose (or even resolve) the problem?
January 29, 2014 at 12:45 am
Do the SSIS packages launch any SQL queries against the source database?
Maybe you can run Profiler while the SSIS packages are running to find out what is going on.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply