article Qlik Replicate Troubleshooting Example: Latency on Hypercluster Azure SQL environment in Official Support Articles

article Qlik Replicate Troubleshooting Example: Latency on Hypercluster Azure SQL environment in Official Support Articles https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Troubleshooting-Example-Latency-on-Hypercluster/ta-p/2047070 <P>A Qlik Replicate task has high latency and fails to start. Blocks were observed on the database and all available processors were consumed for a single, long-running Azure SQL transaction. </P> <P>Errors to look out for:</P> <P class="lia-indent-padding-left-30px"><FONT face="courier new,courier">[SOURCE_CAPTURE ]E: RetCode: SQL_ERROR SqlState: 40001 NativeError: 1205 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Transaction (Process ID 1834) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Line: 1 Column: -1</FONT></P> <P> </P> <H4><FONT color="#339966"><STRONG>Environment</STRONG></FONT></H4> <P class="lia-indent-padding-left-30px"><LI-PRODUCT title="Qlik Replicate" id="qlikReplicate"></LI-PRODUCT> </P> <P> </P> <H3><FONT color="#339966"><STRONG>Resolution</STRONG></FONT></H3> <P><SPAN>Killed the long running transaction on Azure SQL and changed the MAX DOP (see img 01) setting to 8, then task was resumed. After few hours the tasks eventually started functioning as expected and latencies came back to normal.</SPAN></P> <P class="lia-indent-padding-left-30px"><SPAN><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="img 01" style="width: 708px;"><img src="https://community.qlik.com/t5/image/serverpage/image-id/102496i697EAF371035BB37/image-size/large?v=v2&px=999" role="button" title="Database Properties.png" alt="img 01" /><span class="lia-inline-image-caption" onclick="event.preventDefault();">img 01</span></span></SPAN></P> <P> </P> <H3><STRONG><FONT color="#339966">Cause</FONT> </STRONG></H3> <P><SPAN>The root cause that was identified, an update statement on target Azure SQL shown long wait and was blocking all the other transactions. One another reason identified was the MXDOP setting in Azure SQL DB was set as 0.</SPAN></P> <P> </P> Fri, 10 Mar 2023 12:07:03 GMT Dineshan 2023-03-10T12:07:03Z Qlik Replicate Troubleshooting Example: Latency on Hypercluster Azure SQL environment https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Troubleshooting-Example-Latency-on-Hypercluster/ta-p/2047070 <P>Hypercluster Azure SQL environment troubleshooting</P> Fri, 10 Mar 2023 12:07:03 GMT https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Troubleshooting-Example-Latency-on-Hypercluster/ta-p/2047070 Dineshan 2023-03-10T12:07:03Z