QV not going to Secondary Node of SQL Server Availability Group.

[Anonymous]

disclaimer: If this is in the wrong place please feel free to relocate.....

Greetings. For the record I'm not a Qlikview guy at all. I'm a DBA that desperately want to get QV away from my primary server as much as I possibly can.

We're using SQL Server 2012 with an Availability Group (one Secondary). The goal is to make more use of the Secondary wherever possible, like this.

We have:

1. Installed SQL Server Native Client 11.0 driver on the QV server.
2. Created a new ODBC connection to the Primary node of the AG, but set the Application Intent to READONLY.
3. Created a new QV report to use the new ODBC connection.

Unfortunately, the report still hits the Primary node of the AG. I've got other stuff (SSRS, Access) successfully doing the same thing, so I know that the settings within SQL Server itself are fine. However, neither of those use true ODBC connections like QV does, so it's not exactly apples to apples.

I also found this issue, and have attempted the workaround, to no avail.

Any ideas?

Thanks!

[Anonymous · Accepted solution]

This is resolved -- The issue was that the default DB MUST be set to a DB in the AG in order for this to work as expected.