December 10, 2018 at 10:39 am
Hi all,
we have SSIS packages deployed on SQL Server 2016 Enterprise Edition, 3 of packages are scheduled on every 15 min which is used for pulling data from SQL Server to SQL Server, most of times they failed with 'The operation failed because the execution timed out', BI team advised me to look into SQL Server side for this.
I have looked for Remote Query Timeout Option which is already set to 0
is there any other factors or settings do I need to take into account from SQL Server side?
Thank you.
December 10, 2018 at 3:25 pm
Shree_L - Monday, December 10, 2018 10:39 AMHi all,
we have SSIS packages deployed on SQL Server 2016 Enterprise Edition, 3 of packages are scheduled on every 15 min which is used for pulling data from SQL Server to SQL Server, most of times they failed with 'The operation failed because the execution timed out', BI team advised me to look into SQL Server side for this.I have looked for Remote Query Timeout Option which is already set to 0
is there any other factors or settings do I need to take into account from SQL Server side?Thank you.
The BI team needs to review the packages and determine what task is taking too long to process. Once they have identified that task - and the code that is being called - then you can review the activity in SQL Server to see if there are any other processes that could be blocking.
If these processes have been running for a while with no issues - then it is likely that either some other process is blocking - or the execution plan for the code changed and the new plan is not working very well. If these are new packages then it is likely they are timing out due to the code they are running.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply