scotdg (2/12/2016)
I guess I didn't see how it helped because I had already made sure that the system account login in SQL server has access to the database.
Just to clarify, it's the SQL Server Agent service account you need to be worried about, not the SQL Server service account. Just checking...
I also created a credential from my user account and a proxy but it still does not work.
That only helps if you linked the proxy account to a job step. Can you script out and post the Credential (minus passwords of course), the Proxy Account and the Agent Job that uses it so we can have a look?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato