Join the Conversation
- Find Answers
- :
- Apps & Add-ons
- :
- All Apps and Add-ons
- :
- All Apps and Add-ons
- :
- Re: DB Connect, MSSQL Availability Group, Read Onl...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am trying to connect 3.1.2 to a off-node in a 3 host MS-SQL Cluster. The reason for this is to take load off of the live cluster node. The DBA has assured me that the Availability group flag is set to allow read only connections to this node. I believe him because the error message changed from the last time I tried to connect.
From this.
The target database ('DatabaseName') is in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability group replica is not enabled for read access......
To this
The target database ('DatabaseName') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online."
The DBA has asked that I simply insert -Kreadonly into the connection string. The closest thing I can see to do that in DBConnect is the little check box for "read only". This does not work.
I have also tried editing the JDBC URL to include ;readonly=true with no success.
Anyone run into this before?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you please try with ApplicationIntent= ReadOnly, I never played in this type of environment but it might work.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you please try with ApplicationIntent= ReadOnly, I never played in this type of environment but it might work.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It did. Funny thing is that I had tried in the JDBC URL ApplicationInten= ReadOnly before coming here to post this question and it did not work. Only in a group webex did someone notice the missing "t".
If you convert your comment to an answer I'll gladly mark it accepted.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Where do you specify the ApplicationIntent=Read Only option? I do not see optional connection parameters in the DBConnect Input GUI.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In order to get this working, in the DBConnection definition, Edit JDBC URL needs to be checked and the additional connection string parameter gets added at the end of the string. ApplicationIntent=ReadOnly
ex: jdbc:sqlserver://YourServerName:1433;databaseName=YourDatabaseName;selectMethod=cursor;integratedSecurity=true;ApplicationIntent=ReadOnly
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas
What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)
Automating Threat Operations and Threat Hunting with Recorded Future
