| Author |
Topic |
|
saidtak
Starting Member
6 Posts |
 Posted - 2010-12-20 : 18:58:08
|
| Can I get some help with the best way to debug a failed scheduled job other than reading the error message in the Job History window?Thanks in advance.S.B. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
saidtak
Starting Member
6 Posts |
Posted - 2010-12-20 : 19:23:33
|
| Yes, u r right, but most of the time it doesn't help much! This is what I get when the job fails: The job failed. The Job was invoked by Schedule 82 (PostgresToMsrReduced). The last step to run was step 1 (PostgresToMsrReduced).S.B. |
 |
|
|
saidtak
Starting Member
6 Posts |
Posted - 2010-12-20 : 19:27:26
|
| I was hopping there is something like "sysjobstepslogs" in 2005 !S.B. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
saidtak
Starting Member
6 Posts |
Posted - 2010-12-20 : 19:46:14
|
| Right, the job basically imports data from a postgres database to sql 2000.So there is nothing to set up to get more info in the logs? what about that "Output File" option in the advanced Edit Job Step window?S.B. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
saidtak
Starting Member
6 Posts |
Posted - 2010-12-20 : 20:10:21
|
| I see...what about from the query side! is there a sql statement I can add to the query to generate more info to the output?S.B. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-12-20 : 20:34:01
|
| Does the job execute a DTS package to perform the import? If so, have the DTS log to a file. This will give detailed messaging. |
|
|
|
saidtak
Starting Member
6 Posts |
Posted - 2010-12-20 : 20:35:59
|
| I am afraid I can't do that with the company policy! Thank u so much Tara.S.B. |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-12-20 : 20:51:52
|
| Well, what method are you using to do the import? |
|
|
|
|
Debuging Scheduled Jobs