November 23, 2003 at 4:42 pm
Hi All,
I need some help with some DTS packages we're running.
Basically we have a master package, that calls (execute pkg task) several, 69 in fact, child packages. Each of these child packages are identical, in that they have been created via code and contain a custom task that generates the sql that they are to run, on the fly. The sql is to be executed against an ODBC database, that is referenced by using a SQL connection and we have a permanent linked server for the odbc DB.
What can and does happen regularly, is that we kick off the master pkg, which starts executing the child packages (in parallel). It will run along happily for some time, but on any (ie it's random) given package, it will 'fail'. By failing, I mean that both the master and child package indicate (check sysdtspackagelogs) that the package is still executing, but neither the remote (odbc) server, nor the local (mssql) server have any activity occuring.
No errors are ever logged to the sysdtspackagelog table.
Ideas? Anyone seen this before too?
Any ideas or suggestions are welcome!
Steve.
Steve.
December 2, 2003 at 12:00 pm
This was removed by the editor as SPAM
December 3, 2003 at 9:18 am
You might want to try running the dynamically generated sql in Query Analyzer. We had a similar occurance where the DTS packaged seemed to hang, but when we ran the stored proc (which was fine) in QA we found that there was a disk space error.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply