May 16, 2016 at 1:11 pm
Hi All,
I'm facing an odd situation in one of our servers (runnig ssis 2014 + SQL server 2014).
this is the scenario:
The server A has a package that access the server B (using oledb connection) and copy a considerable amount of data (5GB).
This package runs everyday since the begining of this year.
Today, this package (without any change/intervention) became very very slow.
This package contains a simple Data Flow Task , that performs the copy from server B > A (there's no loop, transformation,etc)
I've started an investigation:
1. When i run the package from my machine (in visual studio), the package runs with the regular performance.
2. If i run the package with the service account (job or ssis catalog) the package is slow
The server B (where the data is transfered from) has the resource governor enabled. I made a test, disabling the resource convernor, and the package still show slowness (only if i use the service account).
One more thing: when i'm using the service account to start the package, the server B (where i run the package and where the data will be stored) doesn't seem in use (there's no cpu, memory or disk consume) and in the server B (the source),SQL server shows ASYNC_NETWORK_IO wait for the query that the package is executing.
But if i use my account (with SA permission in both servers), the package runs ok and the resources are used.
I'll ask for our sysadmins to create another service account, but first i wanna know why this is happening..
Does anyone else have/had a problem like this?
Thanks,
Luiz
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply