August 18, 2003 at 7:09 pm
Is it ok/safe to revoke public select access to all the system tables ?
August 18, 2003 at 8:01 pm
I don't think so. Just off the top of my head, I think you'll get Enterprise Manager users screaming.
I'm sure the repercussions are a lot more serious than that, but I'm not sure just how bad. You'll need to try it out on a test server.
Cheers,
- Mark
Cheers,
- Mark
August 18, 2003 at 11:40 pm
The Only problem I can see could be locks. Users, when they have access to a table they may write complecated queries, using cursors and table locks so that others may suffer.
Other than that as far as I know there wont be any issues.
So if you are sure that you don't have users who think themselves as DBAs, you can give access.
Other wise give access to Information_Schema views
G.R. Preethiviraj Kulasingham
Chief Technology Officer.
Softlogic Information Systems Limited,
14 De Fonseka Place,
Colombo 05.
Sri Lanka.
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
August 19, 2003 at 8:56 am
quote:
Is it ok/safe to revoke public select access to all the system tables ?
This really depends on the application you're using to connect to the database. If it's a custom app, then in most cases yes. You'll need to keep around a couple of things in master, but not in user databases. If you're talking access and the like, then disabling access to sysdatabases and a few other system tables will break you.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
August 19, 2003 at 8:37 pm
The apps running on the server are written in house.
Why do public require select access to system tables ?
For some tables ok, there may be a need. But for public to have access to tables sysusers, sysobjects etc etc it seems a bit crazy...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply