Hi team,
I am encountering a timeout issue when moving large tables. The problem seems to be originating from the cleanup stored procedure (clean sp), as smaller tables are processed without incident.
Could you please look into this issue?
Solved
Timeouts on Data integration
Best answer by Thomas Lind
Hi
When you experience timeouts on the cleansing step, it can also be a benefit to apply Batch Data Cleansing.
I have two relevant links regarding that.
The point as to why this helps is that the timeout is reset for each batch that is being cleansed. So it will be allowed to run for longer without having to increase the command timeout.
+8Hi,
what are the timeout settings for your setup? In 20.10.x you can right-click a data warehouse > edit data warehouse > command timeout in TDI this is a setting in the Portal on your Prepare instance. The command timeout represents the time an operation is allowed to take, the connection timeout represents the time allowed for the establishment of a connection.
What you usually want to do is set up a timeout such that it is long enough to give some headroom for unforeseen slowness, but short enough to be able to throw an error and avoid a process hanging forever.
+5Hi
When you experience timeouts on the cleansing step, it can also be a benefit to apply Batch Data Cleansing.
I have two relevant links regarding that.
The point as to why this helps is that the timeout is reset for each batch that is being cleansed. So it will be allowed to run for longer without having to increase the command timeout.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
