ODBC End-point performance issue for Actian Vector DB

[quan_phan_insightsoftware]

We have been recommended to use ODBC end-point for an Actian Vector DB as target, instead of Vector type endpoint as the latter is get moved out of support.

While using the ODBC end-point for replication we see a pronounced drop in performance. When replicating the same tables from the source and same target - following is the times taken for full replication :

Actian Vector end-point :  1 minute (approx)

ODBC end-point : 11 minutes (approx)

Looking at the processes running on the system during replicate it seems that the latter is not using the VWLoad Utility - which the former is doing for some parallel processing.

Is this expected ? And if so, can there be a fix for this ?

Regards,

Sumeet Ganguli

[john_wang]

Hello Sumeet, @quan_phan_insightsoftware ,

Thanks for you reaching out!

You are right - the native Actian Vector DB driver performance is much better than the generic ODBC target, there are many factors include the native driver utilizes VWLoad Utility to do Full Load and write net change tables etc. However in general ODBC the Full Load is done via INSERT SQL operationss, that's why it's slow.

If switch from native driver to generic ODBC driver, then the syntax should be custom and adjust, we may let the generic ODBC driver to use the VWLoad Utility as well or work in a similar way. In general the steps are:

1. Export the syntax of the native Actian Vector DB driver

2. Make a new ODBC syntax (eg name 'VECTORODBC'), and migrate the native driver commands/SQLs/utilities to the ODBC syntax, include the data type mappings etc

3. In Replicate general ODBC Target endpoint, use the syntax 'VECTORODBC'.

Anyway, there are many steps and tunings should be should be take into account , I'd love to suggest Professional Service Team involved.

Hops this helps.

Regards,

John.