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 |
|
greglamp
Starting Member
2 Posts |
 Posted - 2005-09-28 : 10:59:43
|
| If I create a login on my SQL server for a user and only give them access to one database on the server is there any tool that can be used to ensure that they do not run scripts that over burden the server? |
|
|
chiragkhabaria
Master Smack Fu Yak Hacker
1907 Posts |
Posted - 2005-09-28 : 11:18:33
|
| you can on the profiler and check what script is runned by the user .. and what was the cpu consumption and all the details.Complicated things can be done by simple thinking |
 |
|
|
greglamp
Starting Member
2 Posts |
Posted - 2005-09-28 : 11:27:59
|
| I am looking for a preventative approach. More like a way to place a governor on how much processor the login can use and to avoid table locks by them. |
|
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2005-09-28 : 12:15:23
|
| You could create a 'looping' piece of code to identify "high_activity connections" created by "a defined set of users" and then issue a "kill spid" command....very crude, but may be effective.however the "looping code"...could become your performance killer unless coded to take "breaks".preventative measures....give them access to a 'reporting only' database...with access to data via pre-coded SP's! |
|
|
|
X002548
Not Just a Number
15586 Posts |
|
|
|
|
|
Allowing Access While Preventing overuse