May 26, 2010 at 10:59 pm
Good day,
In SQL Server Management Studio, under SQL Server Agent >> Jobs, i can see the Integration Services jobs from there. Going into the Job Properties i can see on the left panel the connection information, namely the Server\Instance Name, and Server\Username. Is the Server\Username saved in this connection info the login credential used for execution?
My objective of confirming this point is because there's a need to change the login credential for all the SQL Server Agent Jobs. If the login is really the one saved in the connection, how should i go about changing it? The GUI itself does not allow changes, so i need help on the possible methods to have this changed.
May 27, 2010 at 8:47 am
The login you see as domain\username is your connection to the instance you're viewing and isn't used in execution of the job.
Typically, a job is run under the credentials of the login that runs the SQL Server Agent service, but if the job has a proxy owner, it will run under the credentials of the proxy. You can change the service account in SQL Server Configuration Manager.
Greg
May 30, 2010 at 7:59 pm
Hi Greg,
thanks very much for the clarifications.
i understand from the manuals, that the scheduled execution of integration services (packages for analysis services) is related to the security credentials under Security >> Credentials, which means, each time a password is changed for the login used, the password has to be updated under this security credentials side.
if i understand correctly what you told me earlier, the jobs for integration services should be using the service account that starts the SQL Server Agent. well i'm a little confused on which login / account would be picked actually, the service account that started SQL Server Agent, or the account saved in the security credentials.
thank you.
June 1, 2010 at 9:45 am
By default, jobs run as the SQL Agent service account. You would create a credential and proxy if you wanted to have the job started by an user account. The credential relates the user's login to a login that has permission to execute steps in the job.
For example, I have an SSIS job that needs to be started on demand by a user application. I granted the user permission to run sp_start_job and created a credential that relates the user to the login that runs the SQL Agent service. Then I created a SQL Agent proxy for SSIS Package Execution and defined it using the credential.
Greg
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply