I spent quite a few hours trying to figure out why DNS wasn't starting. Finally found these links.
https://www.reddit.com/r/sysadmin/comments/4iut0f/heads_up_win2008_r2_microsoft_update_kb3145126/
https://community.spiceworks.com/topic/1575385-windows-2008-r2-kb3145126-killed-dns
https://social.technet.microsoft.com/Forums/windowsserver/en-US/b54da90c-21b5-475c-bc33-f05fa742229c/kb3145126-causing-dnsexe-crashes?forum=winserveripamdhcpdns
I uninstalled the update and DNS is working again. Ugh!
Wednesday, May 11, 2016
Tuesday, May 3, 2016
SQL match orphaned users after DB restore
Restoring a DB to another DB server will not restore users to the SQL server itself, only the users in the DB. But to use those users, they will need to be created in the SQL server and then mapped to the appropriate user in the DB.
Quick notes on how to do this.
List the orphaned users:
Fix the users
More Details here.
https://msdn.microsoft.com/en-us/library/ms174378.aspx
Quick notes on how to do this.
List the orphaned users:
use RestoredDBName
EXEC sp_change_users_login 'Report'
Fix the users
use RestoredDBName
EXEC sp_change_users_login 'Auto_Fix', 'user'
-or-
EXEC sp_change_users_login 'Update_One', 'OrphanedUser', 'OrphanedUser'
More Details here.
https://msdn.microsoft.com/en-us/library/ms174378.aspx
Subscribe to:
Posts (Atom)