November 29, 2010 at 7:42 am
Hi
I would like to provide my database users(has only read access to the databases) previlage to use certain DBCC commands and i understnad most of them can only be used by sysadmins or db owners but is there a way i can provide them by creating some stored procs which can be "Executed as" sysadmin.
November 29, 2010 at 7:49 am
Sounds like a good test case.
Can you post the code you have for that proc so that we can check it out?
Also why do you want to give them that information? It seems something more up your alley.
November 29, 2010 at 7:56 am
Which DBCC commands and what's the reasoning behind this?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 29, 2010 at 8:00 am
GilaMonster (11/29/2010)
Which DBCC commands and what's the reasoning behind this?
I just hope it's not about shrinking ;-).
November 29, 2010 at 8:03 am
I havent started anythign on this but i would like to give some commands like " show statistics" and some other which are not harmfull but provide them information about all databases.
November 29, 2010 at 8:05 am
Ninja's_RGR'us (11/29/2010)
GilaMonster (11/29/2010)
Which DBCC commands and what's the reasoning behind this?I just hope it's not about shrinking ;-).
🙂
Not too many DBCC commands that I could think would be really useful to end users
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 29, 2010 at 8:14 am
Tara-1044200 (11/29/2010)
I havent started anythign on this but i would like to give some commands like " show statistics" and some other which are not harmfull but provide them information about all databases.
I'll have to second Gail here... I just don't see how usefull that can be for the non-initiated. And then again this is usefull only before doing something about the problem at end in a scheduled job... from there you can always keep a log and report of that.
That's the only real use I can see here.
November 29, 2010 at 8:22 am
Ninja's_RGR'us (11/29/2010)
And then again this is usefull only before doing something about the problem at end in a scheduled job...
Or maybe when trying to diagnose the reason for poor query performance. But that's not something that one can do without a fair bit of knowledge of query optimisation and processing
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 29, 2010 at 8:29 am
GilaMonster (11/29/2010)
Ninja's_RGR'us (11/29/2010)
And then again this is usefull only before doing something about the problem at end in a scheduled job...Or maybe when trying to diagnose the reason for poor query performance. But that's not something that one can do without a fair bit of knowledge of query optimisation and processing
...a nd I'm not saying this would be impossible, but it's kind of hard to do anything about a rogue procedure without having lots of privileges. :hehe:
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply