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 |
kevindrys
Starting Member
7 Posts |
Posted - 2007-06-13 : 15:29:01
|
This may be an intuitively obvious question, and if so, I apologize.Speaking in terms of best practices here, what is the preferred method for allowing developers to work with databases in SQL Server? If they use Management Studio, then they have access to tools for perhaps messing with other databases, etc. that they should not (assuming it is not correctly secured). Likewise with Enterprise Manager. I can see where they would use Query Analyzer, but these two are now combined in Management Studio.I'm just inquiring into how other DBA's do this. I realize there are DBA's that are developers and vice-versa, but what if there is a clear line of distinction and you want to keep the tools used in these roles separate?Thanks in advance.Kevin |
|
jsmith8858
Dr. Cross Join
7423 Posts |
Posted - 2007-06-13 : 15:44:37
|
>> (assuming it is not correctly secured)If you correctly secure your databases, it doesn't matter what tool they use. In fact, even without any of those tools, just using QA or Visual Basic or even Access or Excel, they can mess with *any* database they can connect to if it is not correctly secured. The solution: give the developers all the tools they need, and secure your databases properly. - Jeffhttp://weblogs.sqlteam.com/JeffS |
 |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-06-13 : 21:56:36
|
Agree, people access db based on permission they have no matter which tool used. |
 |
|
kevindrys
Starting Member
7 Posts |
Posted - 2007-06-14 : 10:32:22
|
That's pretty much what I thought. Thanks much!Kevin |
 |
|
|
|
|
|
|