SQL Server 2005 Agent - User Account

Who needs to invoke the jobs in SQL05? Manually executing the job import_myteam as a user with dbo privileges fails. So, which user account should be assigned to successfully run scheduled jobs (ie, dbo)?

The package file for the job in question is located in the server€™s C:Documents and SettingsuserxyzMy DocumentsVisual Studio 2005ProjectsIntegration Services Project3Integration Services Project3MyTeam (1).dtsx, but this still fails when the user userxyz is logged on and is executing the job directly from the server console.

Step1 of the package executes as userxyz
Step 2 fails and runs as cpmc-casql02

The user account userxyz has administrator rights to the server as well as being a sysadmin of the SQL2005 database (named cpcasql02).

The account cpmc-casql02 is a €œpublic€? user of the database and is a member of the administrator group on the server itself.

This same scenario carries for tasks as simple as truncating a table and importing the contents of another table in the same database.

All of these jobs exhibit the same behavior whether run directly from the server console on remotely from a workstation connected to the SQL2005 database.

Attempting to get a really simple job working, we also created a very simple SSIS package which does a select from a database table and writes the output to a text file. When running the same package from the user€™s workstation within Visual Studio, the package executes successfully. Once copied to the server, and run from within SQLServer as MyJunePackage however, the execution fails in the same manner as described above. The first step executes successfully as the logged-in user and the second fails executed under the account cpmc-casql02.

So, again we have the same behavior of sequential steps being run as different users with unsatisfactory results. Please advise as to how to set up these jobs to run correctly and consistently.

Thanks very much,Eric W