Showing posts with label read-only. Show all posts
Showing posts with label read-only. Show all posts

Sunday, March 11, 2012

Database roles

I am not sure if this is the right place for this question or not but here it goes...

I want to add a new user to the database with read-only rights. I know public is selected by default and can not be changed. I also added the user to db_datareader and db_denydatawriter. But just as I was about to save I noticed Read Only. I have done some searching but have not found anything about this role. I assume it does just what it says but I am confused as to why it would be there when I can set the other settings I just did. Is there any benefit to using this role instead of the ones I chose? Should I add this role in addition to the two I have already picked? Any help is greatly appreciated.

thank you,

Kevin

If this is SQL Server 2000, then add them to db_datareader and db_denydatawriter. If this is SQL Server 2005, just grant select permissions on the database to the user.|||If the user is in those fixed database roles then need not worry about setting anything additional, as the user will be in READONLY for data.

Friday, February 24, 2012

Database Read-only

When a database is retired and have to be read-only - only allow user to read tables under retired database however how I can grant to new user login into retired database with read-only. It won't me grant new user login. Only exist login id.
Thanks,
Mark
This problem is caused because the database is READ-ONLY. Meaning you can
not insert new users into the SYSUSERS table because it is READ-ONLY. I
might consider putting the database in DBO-USE-ONLY mode and then removing
the READ-ONLY, insert the new user and the place the database back into
READ-ONLY, and then remove the DBO-USE-ONLY usage. This will keep the
database from being update for normal users, but will also lock them out
while you are updating the database.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mark Call" <anonymous@.discussions.microsoft.com> wrote in message
news:9CCDB045-4AAD-453B-9BAC-24EFC40A976F@.microsoft.com...
> When a database is retired and have to be read-only - only allow user to
read tables under retired database however how I can grant to new user login
into retired database with read-only. It won't me grant new user login. Only
exist login id.
> Thanks,
> Mark
|||Thank you for suggestion.
Thanks,
Mark

Database Read-only

When a database is retired and have to be read-only - only allow user to rea
d tables under retired database however how I can grant to new user login in
to retired database with read-only. It won't me grant new user login. Only
exist login id.
Thanks,
MarkThis problem is caused because the database is READ-ONLY. Meaning you can
not insert new users into the SYSUSERS table because it is READ-ONLY. I
might consider putting the database in DBO-USE-ONLY mode and then removing
the READ-ONLY, insert the new user and the place the database back into
READ-ONLY, and then remove the DBO-USE-ONLY usage. This will keep the
database from being update for normal users, but will also lock them out
while you are updating the database.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Mark Call" <anonymous@.discussions.microsoft.com> wrote in message
news:9CCDB045-4AAD-453B-9BAC-24EFC40A976F@.microsoft.com...
> When a database is retired and have to be read-only - only allow user to
read tables under retired database however how I can grant to new user login
into retired database with read-only. It won't me grant new user login. Only
exist login id.
> Thanks,
> Mark|||Thank you for suggestion.
Thanks,
Mark