Viewing 8 posts - 1 through 8 (of 8 total)
Thanks for the responses. I do notice the SID is different on the secondary server than on the primary even though the login names are the same etc. So since...
February 23, 2010 at 6:56 am
Hi,
The DB is a replicated db due to log-shipping. Isn't it supposed to be in read only standby mode? This is the error I get:
Database 'DB' is in warm standby....
February 19, 2010 at 1:48 pm
Thanks SSC-Enthusiastic
I ran the script on the secondary server master db and received a bunch of errors:
Terminating this procedure. The User name 'db_accessadmin' is absent or invalid.
Msg 15291, Level 16,...
February 19, 2010 at 11:58 am
thanks for the replies. I did as you said but still no dice. I checked the SQL login properties through SSMS and the mapping to the replicated db is still...
February 19, 2010 at 11:48 am
Thanks for the replies. Here are the results:
username groupname login name DefDBName DefSchemaName UserID ...
February 18, 2010 at 8:48 pm
No the login in question can not access this particular DB. It has access to the other replicated dbs on this secondary server.
February 18, 2010 at 2:03 pm
thanks for the replies.
I tried the orphaned users resolutions and this account did show as orphaned but after running EXEC sp_change_users_login 'Auto_Fix', 'user' the account still does not have...
February 18, 2010 at 1:16 pm
Thanks for the reply. To be honest I don't have much detail on this. It's a request from a SQL programmer. She does a lot of enterprise reporting for the...
February 17, 2010 at 1:43 pm
Viewing 8 posts - 1 through 8 (of 8 total)
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy