January 13, 2014 at 6:10 am
I have a package in SSIS 2008. It is taking data from one database and transforming it to another database on the same SQL Server which is not the server that SSIS is on. The package is hanging on a simple SELECT with a lookup. It is stuck on row 68804. When I look in SQL Server activity monitor it looks like the process is still running. I had another incident where the package calls a stored procedure and it looks like it is running from the SSIS side but in Activity Monitor nothing is running. I doesn't matter what the source and destination SQL Servers are and everything was running fine at one point a few weeks ago. Could there be an issue with TempDB? What could be causing this? I know exactly where it is hanging but don't know why so if you could help, I would greatly appreciate it as it is causing me to get behind.
I am getting this warning in the event viewer on the server that is running the package: A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 7258 seconds. Working set (KB): 25572, committed (KB): 72728, memory utilization: 35%%.
January 13, 2014 at 8:33 am
I figured out one of my issues -- one of my inserts was going to the wrong table, causing a lock. Will have to work on the other one now.
January 14, 2014 at 7:05 am
How big is the lookup table? How do you cache it?
Where are the rows you select being written to, and what are the settings on your destination?
Are there any steps (such as unions and sorts) that are waiting for all rows before they process?
January 14, 2014 at 7:33 am
That issue has been resolved but I do have another that hangs where it is calling a stored procedure that uses a cursor -- somebody else wrote the code and I have verified that there are no uncommited transactions.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply