February 3, 2009 at 10:08 pm
I have a Windows scheduled task on one of my data warehouse servers that calls a batch file that runs a number of ETL SSIS packages, using Integrated Security.
If the task is run using the developer's domain credentials then the job performs approximately 3 times faster than if it is run under the service account that runs the database engine service. The performance drop is consistant accross all the packages in the job. I need to move this job to use a service account but I can't afford the time blowout.
It doesn't make sense to me that the account used impacts the performance and I'm struggling to find a cause, let alone a solution. I'm looking for any insight or ideas on how I can progress diagnosis of this issue.
Any advice would be very welcome.
Scott Pettman
February 4, 2009 at 6:53 am
Is it possible that the different connections are changing the ANSI settings? That's the only thing that comes immediately to mind.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 4, 2009 at 1:32 pm
Thanks for the idea. The connection strings are defined in the SSIS package properties so it shouldn't depend on the which account runs it (though it does use the credentials of the account that runs the package). But I'll check it out anyway.
Scott Pettman
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply