I have an SA credentialed connection for both the source and destination
server. Both servers are SQL Server 2000 standard. The job fails with an
"unspecified error" which obviously is little help. I know it is connecting
to both servers as it even shows me which jobs are already present on the
destination server and allows me to check only the ones that are not.

Are there any special issues that might cause this seemingly simple and
straightforward transfer? I do not yet have access to SISS so has anyone had
success transfering jobs with that tool? Are there any other options or third
party tools that can transfer jobs from one server to another?

Thanks,
Don

If you are just transferring jobs, why not script them and run the script at
the destination, after changing any server specific info you need?

--
Kevin Hill
3NF Consulting
www.3nf-inc.com



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

I not aware it could be done by scripting but would actually rather do it
this way providing more documentation of the jobs. Are there any articles
describing how to do this that you can point me to? Could I use something
like Red Gate SQL Compare to do this?

TIA
Don

"Kevin3NF" wrote:

I don't think SQL Compare will help you, as jobs are data in a MSDB table,
not schema.

Scriptin them out and re-running the script is the easiest way to do a
one-time job move.

Right-click the job, all tasks, generate SQL Script (or something like
that...I don't have Enterprise Manager in front of me).

Take the resulting .sql file, open it in a Query Analyzer session connected
to the destination server and execute it.

If you are needing to move the jobs regularly, this is when you would use
DTS. If that is the case I would be interedted in finding out the business
reason behind scheduled job moves...

--
Kevin Hill
3NF Consulting
www.3nf-inc.com
http://kevin3nf.blogspot.com


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

Thanks very much and this worked quite well. I knew I could script regular db
objects but never knew jobs could be scripted as well. Duh!

BTW, I did attempt the same task that failed in DTS by using SISS in SQL
Server 2005 and it also failed. However, the error information was very
helpful and indicated the job owners did not match. So I checked the job
owners on the source DB using the new SQL Management Studio and could see
that several had an NT Auth User as the owner rather than SA. I was able to
change those to SA and then the transfer completed without error. I could
choose which jobs to transfer (or all) and even to overwrite where the
destination job was already present. Worked like a champ.

Thank again.


"Kevin3NF" wrote: