Advanced setting tab for the Microsoft Azure SQL Database as Target

[attunitysupportcs]

In this advanced tab, I would like to clarify more about two parameters

First is the "Use BCP for loading tables"

Question: If I plan to do CDC replication tasks ( Apply Changes), select the "Use BCP for loading tables" will affect the data capture process?

Second is the "Internal Parameter"

Question: What is the effect to my replication task if have select the internal parameter "suspendTableWithComputedColumn". Can you clarify more on this parameter since there are limited sources in the Qlik Website.

Thanks.

[Alan_Wang]

Hi @attunitysupportcs 

suspendTableWithComputedColumn is a default internal parameter that is turned on for some source endpoints such as SQL Server. It suspends a table when a computed column is detected in the source tables. Endpoints such as SQL Server do not support computed columns for CDC so the task will result in errors if one is detected. This parameter suspends just the table in question so the rest of the task can continue replication. If turned off, the whole task will stop from the errors.

[attunitysupportcs]

Hi Alan,

How about the "Use BCP for loading tables"? If I plan to do CDC replication tasks ( Apply Changes), select the "Use BCP for loading tables" will affect the data capture process? The Qlik website written "Use BCP for loading tables: Select this to transfer data for full-load operations using BCP." Is this means the BCP only for full-load operations?

Thanks.

[Alan_Wang · Accepted solution]

Hi @attunitysupportcs 

BCP only affects the Full Load process, not CDC. BCP does have a limitation where if it is turned on, unlimited LOB columns are not supported, even for the CDC process. LOB column sizes would need to be limited or the use of BCP needs to be turned off.

I'm not entirely sure if the use of BCP for Full Loads would be faster or not using BCP. More info on BCP can be found in Microsoft's documentation. 

https://azure.microsoft.com/en-us/blog/bcp-and-sql-azure/