Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
LDR
Creator II
Creator II

Qlik Sense compatibility with MSSQL Server Always On

Hi Qlikers,

I have one question and probably you know the answer.

I have Qlik Sense Enterprise May 2024 running and I would like to create a connection agains a Listener which is part of an Always On SQL service (MSSQL Standard 2019).

So far I understand it must work, isn't it? does anyone already tested it? is there any kind of compatibility issue?

Doesn't it matter if I use the OLE DB connector instead of the SQL Server one?

Thanks in advance

Labels (1)
1 Solution

Accepted Solutions
Jack_Guo
Support
Support

Hi @LDR  Yes, Qlik SQL connector should works, as well as ODBC connector.

View solution in original post

2 Replies
Jack_Guo
Support
Support

Hi @LDR  Yes, Qlik SQL connector should works, as well as ODBC connector.

LDR
Creator II
Creator II
Author

Hi @Jack_Guo  

Sorry because I forgot to come back to my post and give my feedback. Maybe it could be useful for any other Qliker so, I'm going to explain it a little bit more in detail:

  • If we have an Always On SQL cluster, what we probably have is two nodes (two MSSQL Servers).
  • We'll have "Availability Groups" (AGs) where we group the following objects:
    • Databases: one or more databases that will be part of the availability group. In my case I have one by AG but it depends on your requirements.
    • Replicas: MSSQL nodes where each database is present. At least we'll have the primary MSSQL node and the secondary. So, in on node the database is "active" (that's the primary node), and in the other is "passive" (secondary node). The database running in the active node is where any 
    • Listeners: that's an Active Directory object (Computer) with an IP address assigned, and makes easier to any tool like Qlik, to connect always to the node where the database is "active".
  • AGs permit us to get access to any of their databases across the listener. Furthermore, they are the minimum unit that we can use to activate those databases in one node or the other.
  • When the primery node is restarted or the failover is activated, then any AG will be activated in the second node or in any of the secondary nodes.
  • Databases when are running in the primary node, are accepting DML SQLs, and any change is synchronize with their replicas.
  • If we need to connect Qlik to any database inside an AG, we'll use the listener to point to any database inside this AG. Then it won't matter if the database is running in the Node one, two or three because its IP address doesn't change.

Of course, we can find that Qlik is running a heavy query and in the middle of the process, the failover is activated and the AG is moved to another node, in this case, even if the listener IP address doesn't change, the transaction will fail. If we run it again, it will work.

In summary, Always On is a technology 100% compatible with Qlik SQL and ODBC connectors.

Regards