June 26, 2006 at 12:19 am
I used some jobs on MS SQL 7.0 to update the tables in MS SQL 2000 from MS SQL 7.0. For some jobs, the job history shew sucessful but no update on the destination table. When I tried to add a new schedule of the problem job, I found the job succeeded and the destination was updated. I wondered if there was a lock if several jobs were reading from a same table at a same time, and the lock would cause the difference between job history and the actural result in destination.
June 29, 2006 at 8:00 am
This was removed by the editor as SPAM
June 30, 2006 at 3:08 am
When it appears to update but does not this has usually been down to the connection not being what we thought it was.
Reasons for this are :
1. Connection object has database changed but the destination table in the transform includes another database name.
2. The connection is using a DSN. When run from within the DTS it uses one on the client machine, when run in a job it uses that on the server. (This problem occurs when the Enterprise Manager is on a different machine to the DTS package).
I would assume that the user that the job runs as could also affect the connection in the same way as problem 2 but this has not happened to me.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply