In perfect world you are correct, need the windows group login in initial setup to be added as user to db.  This is replicated.  Most of my users with myriad...

that was plan B not a big fan I think I can live with the deny for now users not crossing over between groups

was going to problem is all different types of tools going to this so forcing this may be an issue

no from the OLTP, I was thinking I could use deny on the group login on the OLTP.  However if a user belongs to more than one group and that...

Duh missed the obvious some sysadmin took RO node from 48 gig to 7, so not comparable to OLTP node, please disregard, should have looked for obvious

thanks for teaching very old dog new tricks, I do have a vendor supported database which has all it's db set to this

I am correct that the app has to use a readonly intent for connections?

if I go with #2 is it possible to have a AG with 2 nodes (one as failover and read only intent).  If so if server A fails over can...

all on vmhosts so license not an issue we are set at host levle

Quick question may be if I setup AG with 2 servers with one read only intent, and primary fails, can it fail over to Read only intent?  If so when...

not supported by vendor this is 3rd party app

already in plan to upgrade

problem is this is a 3rd party app, no re-write possible (it is bad code) but has not changed in 2 years.  However recompiling the bad stored proc did solve...

seen this before after an index rebuild, plan becomes a mess, the sql and the indexes did not change, write it off as a feature of MS

that will be my approach will start with biggest tables and work my way through