I have a rather simple SSIS package that, among other steps, is extracting data from a fact table, running it through a split to take out data with a specific value, and inserting it into a temporary table.
When I run the package in debug mode on my machine, it runs fine.
When I run it as part of the ETL in a SQL Server 2012 job, the package hangs on the specific step I referenced above.
If I change the OLE DB Destination to another temp table with the same structure, it runs fine in the job.
The temp table in question is loaded in two packages that precede this one in the jobsteps.
Is there anything I can check to see if this table somehow is being locked by a prior process and not released?