OK -- I've googled this for days now, and I still can't find the answer.
We have a DTS package which does several steps, in one of which it exports data from a view to a text file using BCP. The syntax is:
EXEC master..xp_cmdshell 'bcp SunshineMLS..vwList out \\web\d$\webserv\inclist.asp /c -t"\t" -S SMLSDB'
When I run the job manually, the view exports, just for example purposes, 100 rows of data. I've scheduled the package by right-clicking on the DTS package and selecting "Schedule Package..." The scheduled job works fine every night, and as far as I can tell the other 4 tasks in the DTS Package work fine -- but this BCP export when scheduled only exports 94 rows (again, just for example).
Why would the scheulded version of the DTS export a different # of rows from the View compared to the manually-executed DTS package? Did the act of scheduling a package "compile" a version of the View or its execution path so that if I changed the View a week ago or so, the scheduled DTS is still using the "old" version of the View?
I can't figure it out.
Any suggestions would be appreciated. I've tried re-saving the DTS package and re-scheduling it anew, but the same results.