April 14, 2003 at 8:50 am
if you set up a log shipping to a remote server, after the users are set up and the log shipping has started how do you remove users from those databases without starting and stopping the log shipping
April 14, 2003 at 12:01 pm
I'm guessing you have this setup as a database maintenance plan? I'm guessing you log ship on a schedule. One possible solution would be to schedule a job that runs before the scheduled start time of the log ship. This job would force the users to exit. Maybe by sending an email? Give them 5-10 minutes to exit, then if they are still not out have the job kill their connections. Also, look at the "terminate_users" option of log_shipping_plan_databases stored procedure. This option terminates users from the secondary server.
Darren
Darren
April 14, 2003 at 12:08 pm
that option terminates users who are connected before update, not users in the database. If somebody is fired and i am removing there login it comes of the production server but how do you drop it off the read only log shipped server
quote:
I'm guessing you have this setup as a database maintenance plan? I'm guessing you log ship on a schedule. One possible solution would be to schedule a job that runs before the scheduled start time of the log ship. This job would force the users to exit. Maybe by sending an email? Give them 5-10 minutes to exit, then if they are still not out have the job kill their connections. Also, look at the "terminate_users" option of log_shipping_plan_databases stored procedure. This option terminates users from the secondary server.Darren
April 14, 2003 at 12:14 pm
Oh, now I see. You must only be shipping your user defined database. You will have to ship the master database in order for the user names and permissions to be migrated.
Darren
Darren
April 14, 2003 at 12:54 pm
actually that would only work with syslogins
Sysusers table in the read only database is the problem. I can work on the logins but not the sysusers since the database is in read only. you have to drop the user reference before the login reference
April 14, 2003 at 1:15 pm
You can't log shipping master database. In order to drop user from destination database (by log shipping), you have to drop the user from your original database and run the log shipping jobs in both servers.
April 14, 2003 at 1:16 pm
So when you remove them from production the corresponding change never shows up in the remote server database? I was assuming that the log shipping would handle applying that change to the read only database. Sorry, I'll look around see if I can find anything.
Darren
Darren
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply