happycat59 (8/21/2014)
arnipetursson (8/21/2014)
One more question.If you do not have access to server B beyond db_owner in the database,
how do you ensure that the logins (server principals) are synced?
As db_owner, you cannot do anything except ask someone else to sort it out (e.g. someone with sysadmin or securityadmin priveleges).
You would already need to be doing that - mirroring does not do anything about logins. Logins are at the server level, database mirroring is at the database level.
I've already provided the server owners with a list of jobs and logins I need created on the server. When I failover, all I have to do then is run the update users proc to resync everything. If some logins don't sync because of different SIDs or other issues, I'm db_owner on those databases, so I can just manually add them to the DB after deleting the orphaned login out of the database.
Of course, keeping up with login changes is my responsiblity. Anytime something gets added or removed, I have to communicate that to the server owners. But that's why we use SQL logins and Windows Groups instead of individual logins. When people leave the company or get newly hired, we just make sure they're part of the proper Windows Groups so there's little back and forth on that particular issue.