October 19, 2008 at 8:15 pm
Hi,
I'm currently working on a list of stored procedures which can be safely dropped from my database (assuming that no application uses them), I'm looking for some feedback since I'm relatively new to SQL 2000 and I don't want to make any major mistakes. Suggestions for any other stored procedures that could be dropped would also be appreciated.
Thanks in advance
This is my current list.
o sp_OACreate
o sp_OACDestroy
o sp_OAGetErrorInfo
o sp_OAGetProperty
o sp_OACMEthod
o sp_OASetProperty
o sp_OAStop
o xp_regaddmultistring
o xp_regdeletekey
o xp_regdeletevalue
o xp_regenumvalues
o xp_regremovemultistring
o xp_perfend
o xp_perfsample
o xp_readerrorlog
o xp_revokelogin
o xp_schedulersignal
o xp_servicecontrol
o xp_nmp_raisetrap
o xp_sqlinventory
o xp_sqltrace
o xp_startmail
o xp_subdirs
o xp_dirtree
o xp_availablemedia
o xp_deletemail
o xp_dropwetask
o xp_enumdsn
o xp_enumgroups
o xp_eventlog
o xp_fixeddrives
o xp_getnetname
o xp_logevent
o xp_logininfo
xp_loginconfig
o xp_msver
o xp_perfmonitor
o xp_perfstart
o xp_readmail
o xp_runwebtask
o xp_sendmail
o xp_snmp_getstate
o xp_sprintf
o xp_sqlregister
o xp_sscanf
o xp_stopmail
o xp_unc_to_drive
o sp_sdidebug
o xp_cmdshell
o xp_dirtree
o xp_dsninfo
o xp_enumerrorlogs
o xp_enumqueuedtasks
o xp_findnextmsg
o xp_getfiledetails
o xp_grantlogin
o xp_loginconfig
o xp_makewebtask
- xp_regwrite
o xp_cleanupwebtask
o xp_convertwebtask
o xp_dropwebtask
o xp_enumcodepages
o xp_readwebtask
- xp_runwebtask
o xp_get_mapi_default_profile
o xp_get_mapi_profiles
October 19, 2008 at 9:10 pm
Whats the reason behind wanting to drop them all?
Cheers,
Carlton..
October 19, 2008 at 11:28 pm
I am not sure that dropping built-in system procedures and extended procedures is supported, is it?
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
October 20, 2008 at 12:52 am
Dropping of any dB object is not advisable until you have the complete backup. you can rename the sp's till the next next backup.
System sp's are advisable not to drop.
kshitij kumar
kshitij@krayknot.com
www.krayknot.com
October 20, 2008 at 2:04 am
Why not just make sure no one has permissions to execute those stored procedures? That's a lot better than running the risk of breaking an important process becuase a vital sp is missing. Deleting system objects strikes me as a "bad thing".
October 20, 2008 at 9:31 am
Thanks for the replies.
Carlton Leach (10/19/2008)
Whats the reason behind wanting to drop them all?Cheers,
Carlton..
I wanted to harden the SQL Server as much as possible without removing too much user functionality
krayknot (10/19/2008)
Dropping of any dB object is not advisable until you have the complete backup. you can rename the sp's till the next next backup.System sp's are advisable not to drop.
Ross McMicken (10/19/2008)
Why not just make sure no one has permissions to execute those stored procedures? That's a lot better than running the risk of breaking an important process becuase a vital sp is missing. Deleting system objects strikes me as a "bad thing".
hmm, I didn't think of both, I'll test it, then come back, hopefully with good results.
Thanks again for the help. 🙂
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply