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 |
|
foxman
Starting Member
1 Post |
 Posted - 2004-10-27 : 22:26:20
|
| hi everyone, well i'v been working with only sql-server databaes tables for a couple of months now ... but never with security issues .. ! can anyone tell me how i can password protect a newly created database on my machine which can not be accessed from the enterprise manager .. i mean i dont want anyone to be able to open or even view the database or at least not be able to open any tables from the enterprise manager .. is that possible ... if yes can anyone tell me the procedure to doing that !thankx alotVijay |
|
|
Kristen
Test
22859 Posts |
Posted - 2004-10-27 : 22:54:01
|
| Anyone who is sysadmin will be able to open your database.So I suppose the answer is not to have sysadmin rights ... and then to grant dbowner rights to anyone who you WANT to be able to manage your database (create tables etc.).Then you can grant access rights (read/write or something more specific/exotic) to individual users, or for an application.But I doubt that that helps with your problem!Kristen |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-10-27 : 22:55:04
|
quote:
Originally posted by foxman
hi everyone, well i'v been working with only sql-server databaes tables for a couple of months now ... but never with security issues .. ! can anyone tell me how i can password protect a newly created database on my machine which can not be accessed from the enterprise manager .. i mean i dont want anyone to be able to open or even view the database or at least not be able to open any tables from the enterprise manager .. is that possible ... if yes can anyone tell me the procedure to doing that !thankx alotVijay
1. you can uninstall client tools on all workstation except yours and the server2. check permission in BOL, you may want to strip off public role to minimum and remove guest account, built-in administratorscaution: don't forget to create your account with sa privilege, change sa password and don't forget that password or write it down.--------------------keeping it simple... |
|
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2004-10-30 : 19:22:19
|
| JenNot sure that your first suggestion entirely solves the problem. Some colleagues of mine (who I may have referred to elsewhere) tried this with a database they setup, it didn't stop access to it via Access, Excel etc. It took them about 3 or 4 weeks to solve this problem as they refused to talk to me about it! During which time there were a number of discussions regarding security as the database held confidential informationsteveTo alcohol ! The cause of - and solution to - all of life's problems |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2004-10-30 : 22:28:46
|
Shouldn't be too hard to lock people out as long as they don't have the sa password.  Even that's not too hard to fix, if you change it on them and don't tell them |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2004-11-01 : 22:10:32
|
quote:
Originally posted by elwoos
JenNot sure that your first suggestion entirely solves the problem. Some colleagues of mine (who I may have referred to elsewhere) tried this with a database they setup, it didn't stop access to it via Access, Excel etc. It took them about 3 or 4 weeks to solve this problem as they refused to talk to me about it! During which time there were a number of discussions regarding security as the database held confidential informationsteveTo alcohol ! The cause of - and solution to - all of life's problems
elwoos again? ha ha ha...you should just lock them out through permissions, if they need some data, provide them with minimum permissions on views, sprocs.but in your case elwoos, this might be trouble for you, "knowing" the type of people you work with.--------------------keeping it simple... |
|
|
|
|
|
|
|
|
password protecting a database