Our DBA Team has deemed that any/all SPs/Functions, that were previously public, now require a business justification for enabling permissions; even on Development Servers. Recently SP_Who2 was even deactivated.
I am looking for a list of recommended system functions/procedures taht should be entitled to developers and support staff. Below is my shotgun approach to stuff I think is nice to have.
Thanks in advance for your input...
sys.sp_who - monitoring and reviewing possible blocking.
sys.sp_who2 - monitoring and reviewing possible blocking.
sys.sp_help - List Tables/Views/PKs/etc.
sys.sp_helpdb - Review DB Size and Status.
sys.sp_helpuser - Dump users for DB with Role Info.
sys.sp_helprolemember - List logins for DB Roles.
sys.sp_tables - Dump Tables & Views for DB
sys.sp_table_privileges - Review Table privs.
I bet I am missing some other system objects, perhaps views or tables to list data dictionary related information?
Again thanks in advance for any suggestions...
Steve Medvid
IT Consultant & Web Master
I am looking for a list of recommended system functions/procedures taht should be entitled to developers and support staff. Below is my shotgun approach to stuff I think is nice to have.
Thanks in advance for your input...
sys.sp_who - monitoring and reviewing possible blocking.
sys.sp_who2 - monitoring and reviewing possible blocking.
sys.sp_help - List Tables/Views/PKs/etc.
sys.sp_helpdb - Review DB Size and Status.
sys.sp_helpuser - Dump users for DB with Role Info.
sys.sp_helprolemember - List logins for DB Roles.
sys.sp_tables - Dump Tables & Views for DB
sys.sp_table_privileges - Review Table privs.
I bet I am missing some other system objects, perhaps views or tables to list data dictionary related information?
Again thanks in advance for any suggestions...
Steve Medvid
IT Consultant & Web Master
