Make Connection Timeout value configurable
I am randomly getting the following error:
'Error: Comparison of 'Scripts.state' and 'MyServer.MyDatabase' failed. Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections.
When I re-run SQL CI with exactly the same parameters, next time it works.
Can you make 'Connection Timeout' value configurable from command-line please?
Andrzej Jakuszyk
shared this idea
DLMAv2 cmdlets now have a timeout parameter so you can specify your own connection timeout.
-
Richard Macaskill
commented
Hi Andrzej,
Thanks for the suggestion.Can I check something with you? Does this MSDN question describe your scenario; https://social.msdn.microsoft.com/Forums/en-US/2b71a9b8-5089-4c47-99ca-f466e9c5e1fa/what-is-causing-this-the-timeout-period-elapsed-during-the-postlogin-phase?forum=sqlintegrationservices ?
Particularly the comment from the responder; "Assuming it is intermittent, and not a connection string issue, this is almost always an "out of resources" issue on the SQL Server causing it not to be able to respond to the login request. Check your CPU/RAM and Disk IO performance counters during the failure time."
Are you dealing with remote or low-spec servers?
We may be able to schedule this in some upcoming work on the API, but first I wanted to understand your situation better.
Regards
Richard Macaskill
Product Manager, DLM Automation
Redgate