You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
A cross-server database restore needs to fixup database_principals that do not link correctly to server_principals.
Describe the solution you'd like
New Option @FixOrphanUsers BIT = 1. If 1, once restore is complete, sets database_principals.principal_id to the value of server_principals.principal_id where database_principals.name = server_principals.name.
Describe alternatives you've considered
Alternatively, this could be a separate procedure. But it really only has utility after a cross-server database restore, so it seems to be a natural fit in a restore procedure.
Are you ready to build the code for the feature?
Yes, the code is not difficult and we have coded it in existing procedures.
The text was updated successfully, but these errors were encountered:
sqlslinger
added a commit
to sqlslinger/SQL-Server-First-Responder-Kit
that referenced
this issue
May 1, 2023
Is your feature request related to a problem? Please describe.
A cross-server database restore needs to fixup database_principals that do not link correctly to server_principals.
Describe the solution you'd like
New Option @FixOrphanUsers BIT = 1. If 1, once restore is complete, sets database_principals.principal_id to the value of server_principals.principal_id where database_principals.name = server_principals.name.
Describe alternatives you've considered
Alternatively, this could be a separate procedure. But it really only has utility after a cross-server database restore, so it seems to be a natural fit in a restore procedure.
Are you ready to build the code for the feature?
Yes, the code is not difficult and we have coded it in existing procedures.
The text was updated successfully, but these errors were encountered: