Kind of an odd-ball request but it thrown on my plate...For the most part, our development staff very limited access to our production database... But they do have access. I've been asked to find a way to limit that access to the secondary copy of our AG.I'm aware that we can use "ApplicationIntent=ReadOnly" when connecting and developers are "encouraged to use it... That said humans tend to be forgetful, lazy or a combination of the two (myself included)...Are any of you aware of a way to limit, by either user or role, access to the secondary copy only?Failing that, is there a way to default the connection to use ApplicationIntent=ReadOnly, so that the user would have to actively choose the primary copy?Thanks in advance,Jason
↧