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 |
|
victoriaree
Starting Member
2 Posts |
Posted - 2012-01-20 : 17:17:20
|
| SQL Server 2000Have a job that has ran successfully for a long time. Recently the job failed.If you run the job - says it completed successfully - however - there are no results.If you run the DTS package it runs successfully with correct results.If you execute the stored_proc via EXEC cmd - no resultsI can't figure what is causing the failure of the job or the EXEC cmd. If I can provide more information I will be happy to. |
|
|
sunitabeck
Master Smack Fu Yak Hacker
5155 Posts |
Posted - 2012-01-21 : 07:15:08
|
| I am not very familiar with SQL 2000, so what I am about to say may not be using the exact terms used in SQL 2000:What I am thinking is that, if you have the ability to run SQL Profiler, you should be able to run the package that runs successfully and observer the SQL query that gets sent to the Server via the profiler. That should help you identify the difference between the package. |
 |
|
|
biswajitdas
Starting Member
44 Posts |
Posted - 2012-01-22 : 17:43:50
|
| Now few things here , you said the dts package sucessfully run from a long time, and recentley failed.1) under which account the job running and calling the dts package , IS recentely somebody change the password.2) the account which the job running and calling the dts package ,- you need to check if any specific folder permission or sharepath permission removed.on the last i can say if the dts releted to any folder check if the account has permission or notSr Sql server DBA/Artitech |
 |
|
|
|
|
|