Job Fails - trying to insert into remote machine
I am trying to capture some data from each of the sql servers and store them into a centralised table. When I do a addlinked server and test the stored procedure at different servers it works perfect. But when I try to schedule it as a job on each sql server, it fails with the following error.
Executed as user: Domain\UserName. Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. [SQLSTATE 28000] (Error 18452). The step failed.
I knew adding the same account in the remote machine will solve this. But I am not sure what domain users are existing in the production environment, since I dont have access, I was told that those are not in a domain. More over there will be no technical person involved in doing this at production, so I need to give the scripts that work perfectly and independently.
I also tried setting an sql user name and password for sql server agent to run as, so that sql server agent runs with the sql userid provided, and the same done on source sql server and destination sql server solves the purpose. But this process needs an sql server agent restart. Since all the servers are participating in replication, I am not sure about the impact of this process on Replication. At any cause replication should not break.
Is there any way I can have this sorted out? There could be different ways of doing it, I wanted the best shortest way to achieve this, as it needs to go into production and needs to be tested well locally.
Any help is much appreciated.
- Vijay G
Strive for Perfection
- Vijay G