1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a 3 ans
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a 2 ans
- demandé il y a 8 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
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?