1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
mostly this could be due to connections from dms are killed or timed out due to backup job. by itself backup command shouldnt disconnect the connection. it basically freezes other db connections for some time.I would suggest using executeTimeout on source endpoint connection attribute in seconds with a value greater than backup time. Being said that do set the remote query timeout to similar value by referring to https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/configure-the-remote-query-timeout-server-configuration-option?view=sql-server-ver15#:~:text=Using%20SQL%20Server%20Management%20Studio,-To%20configure%20the&text=In%20Object%20Explorer%2C%20right%2Dclick,to%20wait%20before%20timing%20out.
답변함 2년 전
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 2년 전
Thank you for the answer. I have added executeTimeout to the source however it hasn't changed the behavior and the task failed again. I have noticed following in the debug logs: [SOURCE_UNLOAD ]D: Setting connection timeout as : '8' (ar_odbc_conn.c:533) Not sure what setting is controlling this parameter. I haven't checked the source DB yet - passed it to the customer.
Hi, It's been some time since posted, but did you or your customer find any solution for this?