topic MSSQL source has SQL Basic availability group and secondary is stand-by in Qlik Replicate

MSSQL source has SQL Basic availability group and secondary is stand-by

jliivak — Wed, 26 Jan 2022 11:45:38 GMT

We have a new source from MS-SQL that is using SQL Basic availability group and the secondary leg is stand-by. We can connect successfully, but when we start the load to logstream. Qlik replicate wants to connect to the standby machine and fails. I have seen that you can use the connection internal parameter for that, but we can't add it, the window is just blank.

Qlik replicate version: April 2020 (6.6.0.571)

Re: MSSQL source has SQL Basic availability group and secondary is stand-by

Steve_Nguyen — Wed, 26 Jan 2022 13:49:31 GMT

@jliivak

what is the error " Qlik replicate wants to connect to the standby machine and fails. " ?

could you provide the task log for review ?

Re: MSSQL source has SQL Basic availability group and secondary is stand-by

jliivak — Wed, 26 Jan 2022 17:31:00 GMT

Failed to connect to replica *Standby node*
RetCode: SQL_ERROR SqlState: 28000 NativeError: 18456 Message: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user *Account that tries to connect*

At the moment we removed the standby node, but we would like to have it.

Re: MSSQL source has SQL Basic availability group and secondary is stand-by

Steve_Nguyen — Wed, 26 Jan 2022 19:01:04 GMT

from our user guide :

When working with AlwaysOn Availability Groups, you need to specify the IP address/host name and access credentials of the AlwaysOn Listener in the Microsoft SQL Server source endpoint settings.

Limitations

The following limitations apply when working with AlwaysOn Availability Groups:

DAG (Distributed Availability Groups) is not supported.
An AlwaysOn Availability Group that requires Replicate to access the backup transaction logs (see below) is not supported when the Replicate has file-level access to the backup log files check box is enabled in the Microsoft SQL Server source endpoint settings.

====

or another option :

Is to add this internal Parameter on your SQL server endpoint.

Change the setting by adding internal parameter: "AlwaysOnSharedSynchedBackupIsEnabled" to skip AlwaysOn configuration.

This will allow the task to connect as if it were a stand-alone server.

Re: MSSQL source has SQL Basic availability group and secondary is stand-by

jliivak — Tue, 01 Feb 2022 08:08:50 GMT

I have found the same, but I can't add it there is only one parameter TlogAccessMode, but I can't add.

Re: MSSQL source has SQL Basic availability group and secondary is stand-by

Steve_Nguyen — Fri, 01 Apr 2022 17:50:40 GMT

@jliivak were you able to find solution.

Re: MSSQL source has SQL Basic availability group and secondary is stand-by

jliivak — Sat, 02 Apr 2022 00:13:20 GMT

Unfortunately no, we still searching for solution

Re: MSSQL source has SQL Basic availability group and secondary is stand-by

Steve_Nguyen — Mon, 04 Apr 2022 12:19:59 GMT

@jliivak it best to open a support ticket , if you are having issue .

if you need setup and implementation then best to engage with Professional Service team .