PRB: Database Marked Read Only Does Not Allow You to Change User Permissions Simultaneously (270664)
The information in this article applies to:
This article was previously published under Q270664 SYMPTOMS
In SQL Server Enterprise Manager (SEM), if a user database is marked Read-only, the database does not allow you to change user permissions simultaneously. The entire transaction in which the user tries to change the database status to Read-only, as well as the user permissions, should be rolled back. However, SQL Server saves the Read-only permissions for the database and does not save the Read-only permission for the user.
CAUSE
The various dialog boxes in SEM are run in order and are totally independent of each other. SQL Server does not allow any permission changes to any database user if the database has been marked Read-only. Setting the database to Read-only has the final authority, and any other changes made to the permissions of users on the database are rolled back.
WORKAROUND
This behavior is by design.
You will not be able to change user permissions in a database that has been marked Read-only.
MORE INFORMATION
Even though the Properties dialog box for the database shows that the database status has been changed to Read-only, the Read-only status is not implemented until you click the Apply button, and then close the Properties dialog box.
| Modification Type: | Major | Last Reviewed: | 10/23/2000 |
|---|
| Keywords: | kbprb KB270664 |
|---|
|