I think it is possible using sp_start_job, but I cannot
get it to work. But, how can I get a job to start another
job on a different server, when it finishes? Can that be
As Narayana pointed out in the other response, you may do this via linked
Be aware that sp_start_job just starts the job; it will not wait for its
execution to complete.
For that, you'd need to set up a primitive messaging architecture of some
kind, and poll for result.
Quote:> I think it is possible using sp_start_job, but I cannot
> get it to work. But, how can I get a job to start another
> job on a different server, when it finishes? Can that be
I am trying to do queries from one server to another (both are running SQL
Server 2000 SP3) and get the error:
Server: Msg 18456, Level 14, State 1, Procedure xxxxxxxxx, Line 45
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
The only way it will work is if I am connected as SA. I have the servers
connecting as Remote Servers and realize that if they were set up as Linked
Servers then I could set up the permission between them. My problem is that
I can not drop them as a Remote Server in order to recreate them as Linked
Servers because I have replication set up between the servers and don't want
to go through the hassle of dropping and recreating replication.
I also have distributed queries going as a scheduled task with the owner of
the scheduled task as SA. These don't work with the same error in their log
Is there some way to change the connection between the servers from Remote
Servers to Linked Servers without having to drop and recreate replication?
8. tricky sql