Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DavidRhodes
Starting Member
40 Posts |
 Posted - 2004-03-04 : 08:21:56
|
| I have 2 databases, lets say db1 and db2 each with there own 'login', dbo_db1 and dbo_db2 respectively. Each of these logins have no 'Server Roles' but have 'public' and 'db_owner' database roles for there own database only.The problem I have is that when I log in using dbo_db1 I have access to the system databases, they can't see each others databases though, eg dbo_db1 can't see db2 and vice-versa which is fine. How do I disallow access for dbo_db1 and dbo_db2 to the system databases? |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-03-04 : 09:43:02
|
| You can add the user and set deny data reader but test it first - you will probably find that this stops the user doing a lot of things.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-04 : 12:48:34
|
| Why does it matter that the users can see system objects? They can't modify anything. As Nigel suggested, you'll find a lot of problems if you deny read on the system objects.Tara |
|
|
|
DavidRhodes
Starting Member
40 Posts |
Posted - 2004-03-04 : 14:23:03
|
| Sorry, I didn't delve that deep, I just presumed that if they could see the list of objects that they could edit them, i'm happy leaving as is now. |
|
|
|
|
|
|
Disallowing access to system db's