Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The REVOKE simulation feature is too dangerous to run on production systems #7

Closed
EitanBlumin opened this issue Dec 2, 2021 · 1 comment
Closed

The REVOKE simulation feature is too dangerous to run on production systems #7

EitanBlumin opened this issue Dec 2, 2021 · 1 comment
Assignees
@EitanBlumin
Labels
enhancement New feature or request

Comments

@EitanBlumin
Copy link
Contributor

Relevant script: PUBLIC role with excessive permissions.sql

Problem: The REVOKE simulation feature is too dangerous to run on production systems.

Suggested solution: Optionally utilize the DBCC CLONEDATABASE command to create a schema-only clone of the database(s) in question, set them to READ_WRITE, and perform the REVOKE simulation in them to discover affected users.
@EitanBlumin EitanBlumin added the enhancement New feature or request label Dec 2, 2021
@EitanBlumin EitanBlumin self-assigned this Dec 2, 2021
@EitanBlumin
Copy link
Contributor Author

This was done as part of commit b27d9b9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@EitanBlumin EitanBlumin

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@EitanBlumin