Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-09-10 : 09:27:21
|
| Michael writes "I created a DTS local package that exports my SQL Server DB to Access (created using the DTS wizard). The job executes without a problem when executed directly from the local package. I then scheduled the package for execution, which added a job under SQL Server Agent. No problem. It will run on demand or when scheduled. This was under SQL Server 7.0 SP2. Now, we have upgraded to SQL Server 7.0 SP4. The job will still execute without a problem, but it will never complete. I checked the Access database and the tables are there. I started Task Manager prior to executing the job and monitored the status of dtsrun.exe. While the export was ongoing, this process was using CPU resources. However, once I saw that all of the tables have been pushed over to Access, dtsrun.exe was still executing but not using any CPU resources. And, the SQL Server Agent job was still executing. Seems like a problem with SP4. Any ideas?" |
|
|
|
|
|
SQL Server Agent Job Keeps Executing