ApplicationIntent=ReadOnly allows updates to a database. - by WebStrands

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 697217 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 10/27/2011 1:38:05 PM
Access Restriction Public


When I make a connection to an AvailabilityGroup with the additional parameter, "ApplicationIntent=ReadOnly", I am able to make updates, inserts and deletes.
Sign in to post a comment.
Posted by Microsoft on 11/9/2011 at 4:17 PM

This is an expected behavior. This happens if your primary node accepts readonly connections (which is the default). You can configure your primary to not accept 'readonly' connections and it will fail the readonly connections so you dont accidentally write/update anything from those clients.

Note: Fundamentally Primary nodes are read/write and Secondaries are readonly and this flag is designed to provide a hint to what the application plans to do. It is not designed to prevent writes, it is designed to fail fast at connection time based on the intent with proper server configuration. It is the application's reponsibility to ensure that 'readonly' applications don't write.