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 |
|
pareshmotiwala
Constraint Violating Yak Guru
323 Posts |
 Posted - 2002-08-29 : 13:14:47
|
| I have a database which has a Standard login. The app. accesses the db through a file dsn with the sql login /password in plain text. The folder where the dsn is, is also shared. Also, this account has fairly wide permissions, almost like a dbo. The users occassionally use this account to run some scripts and circumvent our policies.I am trying to detect and not allow users who use this standard login from outside of the computer department. I cannot restrict the use of IP Address as rest of the network is on DHCP. Can somebody help me?? We do have some segments of network on different subnets, but no clear line has been drawn on that.... |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-29 : 13:22:28
|
| Did you read the original yet?http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=19300A. You can't put triggers on system tables;B. You can't PREVENT unauthorized users from logging in with a common, shared login. You can only kick them out after they've logged in, and as you stated earlier, the damage could already be done by that time.The ONLY way to PREVENT them from logging in in the first place is to get rid of the shared login and using individual logins, or Windows authentication. |
 |
|
|
|
|
|
Triggers on system tables