November 22, 2019 at 8:23 pm
Hi
This is when you are migrating from old server to new server.
Is it better to script out the logins and run the login script on new server?
OR
Use sp_help_revlogin and use the script created as output by sp_help_revlogin? What is the best practise.
Secondly, CREATE LOGIN [Domain\Login] FROM WINDOWS WITH DEFAULT_DATABASE = [master]; REVOKE CONNECT SQL TO [Domain\Login] --- so the revoke is making sure the user cannot use Sql authentication? They can only use windows auth?
Thanks!
November 23, 2019 at 12:16 pm
Hi
This is when you are migrating from old server to new server.
Is it better to script out the logins and run the login script on new server?
OR
Use sp_help_revlogin and use the script created as output by sp_help_revlogin? What is the best practise.
Secondly, CREATE LOGIN [Domain\Login] FROM WINDOWS WITH DEFAULT_DATABASE = [master]; REVOKE CONNECT SQL TO [Domain\Login] --- so the revoke is making sure the user cannot use Sql authentication? They can only use windows auth?
Thanks!
Use sp_help_revlogin to get logins. For database level permission you need to run separate script and capture it from source and run it on target.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
November 27, 2019 at 12:34 pm
This was removed by the editor as SPAM
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply