Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
jliivak
Contributor
Contributor

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

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)

Labels (1)
7 Replies
Steve_Nguyen
Support
Support

@jliivak 

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

could you provide the task log for review ?

 

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
jliivak
Contributor
Contributor
Author

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.

Steve_Nguyen
Support
Support

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.

 

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
jliivak
Contributor
Contributor
Author

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

Steve_Nguyen
Support
Support

@jliivak were you able to find solution.

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
jliivak
Contributor
Contributor
Author

Unfortunately no, we still searching for solution

Steve_Nguyen
Support
Support

@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 . 

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!