Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have upgraded the OLEDB SQL driver on the QlikView Publisher. Now the new connections to the data source are connecting with MSOLEDBSQL.1 provider. This is all working fine but Application Intent parameter is not working. The source database is SQL server in Always On configuration. When the QlikView is connecting to the listener DB node it is not redirecting the request to the secondary nodes based on the parameter ApplicationIntent=ReadOnly. The QlikView version is May 2024. Can anyone help with this.
Not an expert! However, from chat gpt and some googling:
1 - Modify the Connection String:
Application Intent=ReadOnly
with the appropriate spacing.MSOLEDBSQL.1
.2 - Verify SQL Server Configuration:
3 - Test the Connection:
By adjusting the connection string to use Application Intent=ReadOnly
and verifying your SQL Server settings, you should be able to direct QlikView's read-only workloads to the appropriate secondary replicas in your Always On configuration.
Hi
try to check that the connection string used in QlikView explicitly contains ApplicationIntent=ReadOnly along with the MultiSubnetFailover=True (if applicable). You can use the conn string:
Provider=MSOLEDBSQL.1;Server=YourListenerName;Database=YourDB;ApplicationIntent=ReadOnly;Integrated Security=SSPI;
then you can test the connection manually using PowerShell or another query tool:
$connection = New-Object System.Data.OleDb.OleDbConnection
$connection.ConnectionString = "Provider=MSOLEDBSQL.1;Server=YourListenerName;Database=YourDB;ApplicationIntent=ReadOnly;Integrated Security=SSPI;"
$connection.Open()
Write-Output "Connection successful"
$connection.Close()
If this works outside of QlikView but not inside QlikView, then the issue is likely with how QlikView handles this parameter.