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.
osp_OACreate
osp_OACDestroy
osp_OAGetErrorInfo
osp_OAGetProperty
osp_OACMEthod
osp_OASetProperty
osp_OAStop
oxp_regaddmultistring
oxp_regdeletekey
oxp_regdeletevalue
oxp_regenumvalues
oxp_regremovemultistring
oxp_perfend
oxp_perfsample
oxp_readerrorlog
oxp_revokelogin
oxp_schedulersignal
oxp_servicecontrol
oxp_nmp_raisetrap
oxp_sqlinventory
oxp_sqltrace
oxp_startmail
oxp_subdirs
oxp_dirtree
oxp_availablemedia
oxp_deletemail
oxp_dropwetask
oxp_enumdsn
oxp_enumgroups
oxp_eventlog
oxp_fixeddrives
oxp_getnetname
oxp_logevent
oxp_logininfo
xp_loginconfig
oxp_msver
oxp_perfmonitor
oxp_perfstart
oxp_readmail
oxp_runwebtask
oxp_sendmail
oxp_snmp_getstate
oxp_sprintf
oxp_sqlregister
oxp_sscanf
oxp_stopmail
oxp_unc_to_drive
osp_sdidebug
oxp_cmdshell
oxp_dirtree
oxp_dsninfo
oxp_enumerrorlogs
oxp_enumqueuedtasks
oxp_findnextmsg
oxp_getfiledetails
oxp_grantlogin
oxp_loginconfig
oxp_makewebtask
-xp_regwrite
oxp_cleanupwebtask
oxp_convertwebtask
oxp_dropwebtask
oxp_enumcodepages
oxp_readwebtask
-xp_runwebtask
oxp_get_mapi_default_profile
oxp_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