January 28, 2009 at 6:21 pm
Hi Folks,
can you use the transfer login task on a mirrored database. My main concern is that the database is in restoring mode and if a logins default database is not a system database the transfer would fail. Can anyone shed light here?
March 26, 2009 at 9:17 am
Logins do not transfer to a user database. They exist only in master. The task will work to the mirror server as the logins move to the master database.
Users are transferred automatically using the mirror process.
October 14, 2009 at 11:19 am
There is an issue that if a database has a default other than the master you will get tossed the error. I have not been able to work around this. If some one has an idea please fill me in.
October 15, 2009 at 7:55 am
For our DR, we use mirror db's. Part of the DR plan is keeping the Logins up to date on the mirrored server. For example, my dbs are mirrored. When i create a new login and db user, the db user is mirrored over but not the login. So we have scripts that creates missing logins and maps the logins to the db user. We do this during DR testing but not regularly. Anyone else use a better technique?
March 25, 2011 at 11:25 am
I've created a job with two parts that runs on the principal. Part one generates a script that creates/synchronized logins. Part two copies it over to the desktop of the Public user on the mirror. At least that way if any developers forget to notify me of logins that need created or synchronized I have a script sitting on the desktop of anyone who can log onto the server that they can run and quickly synchronize any that may have been missed.
The only time it has actually mattered is when the developers are still using SQL logins and made the default database for the login the database to be mirrored. In that case we can't synchronize ahead of time.
Joe Moyle
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply