I created a new job with just the sql script being executed by isql.exe. 1 cmdexec step. It fails. I have another job where step 2 is an isql command, it is working.
I changed my job so all of the isql.exe steps use osql.exe instead and the job works fine. So at this point, I'm just curious exactly why isql.exe suddenly became an issue.
Main Topics
Browse All Topics





by: stavramaPosted on 2007-12-27 at 23:35:16ID: 20540242
The following link shows all the applications that passed the compatibility test for win 2003 sp2. om/kb/9260 31
http://support.microsoft.c
They include in it the sql 2000 so you dont have to worry logicaly about combatibility. Have you tried to recreate the jobs that aint running?