August 21, 2012 at 7:53 am
Hi, If I run "select * from sys.sql_logins" on my principal and mirrored servers it gives me the exact same results in terms of names, SID, created dates etc. The only discrepancies are with these:
Default database - on the principal it has the user database as the default for the logins, but on the mirrored server the logins list master as default. presumably that is because the mirrored version has a 'Restoring...' status. If there was a failover, would the default database change to be the user DB automatically?
Principal ID - these numbers are slighty out of sync between both servers. Can that be ignored?
I want to know that if mirrored failover occurs, will all SQL logins be fully functioning??
August 21, 2012 at 8:02 am
The key for the SQL Logins is the SID, and since they are the same, there should be no problems. As far as the default database changing on a failover, I'm not sure. The best way to find out is test it a test environment and see what happens.
August 30, 2012 at 11:25 am
rarara (8/21/2012)
Default database - on the principal it has the user database as the default for the logins, but on the mirrored server the logins list master as default. presumably that is because the mirrored version has a 'Restoring...' status. If there was a failover, would the default database change to be the user DB automatically?
Mirroring is at the database level, so no. You'll need to add this to your DR plan. Next time consider creating a shell database, associate each Login with the default database they have on the primary and then initialize your mirroring sessions. That said, it's still a good idea to script things like this out periodically for use after a failover. Just in case anyone has changed their default database on the primary to another mirrored database.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 31, 2012 at 4:38 am
opc.three ,
hope login created dates are matched because of master DB sync?
Regards
Durai Nagarajan
August 31, 2012 at 6:00 am
durai nagarajan (8/31/2012)
opc.three ,hope login created dates are matched because of master DB sync?
Sorry, I do not get your comment. Please clarify.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 31, 2012 at 6:45 am
as the user specified select * from sys.sql_logins datas are matching on both the servers.
is it matching due to master DB mirroring?
Regards
Durai Nagarajan
August 31, 2012 at 8:22 am
durai nagarajan (8/31/2012)
as the user specified select * from sys.sql_logins datas are matching on both the servers.is it matching due to master DB mirroring?
The same except for the two columns mentioned.
No, master cannot be mirrored.
@rarara, are your two instances running under the same domain account?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 31, 2012 at 9:05 am
opc.three (8/31/2012No, master cannot be mirrored.
Thanks, i have read it somewhere , but how did the other details gone to the secondary server?
Regards
Durai Nagarajan
August 31, 2012 at 9:11 am
That's why I asked about the account the partners are running under. In some configs logins go over automatically, in others they do not.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 31, 2012 at 9:38 am
durai nagarajan (8/31/2012)
opc you mis-understood this is not @rarara.i asked my doubt related to that.
I know you're not @rarara. I was answering your question and explaining the line of thinking. While you cannot mirror the entire master DB the logins can be sent across to the partner, it depends on the config.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply