April 15, 2005 at 2:00 pm
Hi,
user logon is WinNT
I have users getting access to SQL server 2000 via ODBC. I know that users individually can be set to read only via security permissions means.
I wish to allow some users to ODBC (DSN) link into tables an read data as they wish.
Is there any way I can set a TABLE or VIEW as READ ONLY, with out having to deal with each user individually security permissions. I will have stored procedure build these tables when new data arrives, so do I need to allow stored procedure to turn on and off properties (??? ie read only) when build data in table ?
Thanks
April 15, 2005 at 3:35 pm
The only thing I can think of right now is to set the Database itself to Read Only (see BOL for process). You would then, of course, have to turn this back off before ANY modifications to the database (and all objects therein) can happen.
Hope this helps,
Darrell
April 15, 2005 at 8:11 pm
I see that a table can be placed in a USER file group. And the file group can be made read only in the same database.
Say primary is the READ WRITE etc file group
Say USERTables is the READ ONLY file group.
The USERTAbles will have to be Turn ON and OFF when data is to be updated.
Is this a good idea ?
April 15, 2005 at 8:49 pm
This is my conclusion, yes one can make filegroups read only. But its best to transfer data for users ODBC to a READ ONLY database. Then access to tables is restricted to those tables that are read only on a single file group in the database.
This removed all pitfalls of redundacy and concurrency issues. ( ie Web site or Intranet sites)
Method to Turn On and Off a read only database for Northwind database.
EXEC sp_dboption 'Northwind', 'read only', True
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply