Hello:

I don't have much information to go on and I am not familiar with SQL jobs
or package files. So, I'm just going to ask.

This client moved locations about ten months ago. And, they got a new server.

Doing so required, of course, a change of DNS name, server name, etc.

Now, despite all of that, most of their SQL Jobs and packages work--both
before the move and after the move.

But, 6 of the jobs no longer run for some reason. Therefore, the packages
that the jobs are based on no longer work.

They have tried every possible thing. They have updated the SQL Server
Authentication for the package file, change the owner of the jobs to "sa",
etc.

And, the SQL code that the jobs are based on have not changed.

So, on a real basic level, what sort of things could have happened to cause
the jobs to not work?

They are each really simple one-step jobs, at that.

Thanks!

childofthe1980s

Change in the water? An error message would help.


"childothe1980s" <childothe1980s (AT) discussions (DOT) microsoft.com> wrote