We have Server A and Server B .... within the AG group ..... 15-20 all databases all synchronized (during a dry-run from older 2005 server). They have their own storage (share-nothing)
Now we are going to go production soon on the AG pair ... which means either A or B may be serving into the AG's Listener in a totally random fashion.
Where is what I don't understand: we need to implement some agent jobs (copy from the 2005 server); and some of them do send eMails out when the job\report is completed, etc.
My gut feeling says between the A and the B server, all server login's and server roles, all msdb + model databases, and all SQL Agent Jobs should be kept identical, right?
But in that case if databases in Secondary B are not readable (not read-only because deliberate configuration to save money on licensing) and if the Agents on B are active; wouldn't they want to fire off on and generate error if Node B is secondary.
Would you know a good and concise documentation where the common properties should be configure and maintained in case Server B becomes the Primary node.
Thank you!
Travis McGee