MSSQL security settings for Server Security Settings

MSSQL Security Settings: delete SQL statements with security issues. This is comprehensive. Everything is safe!
The permission to corrupt shell, registry, and COM components is deleted. Copy codeThe Code is as follows: use master
EXEC sp_dropextendedproc 'xp _ export shell'
EXEC sp_dropextendedproc 'SP _ OACreate'
EXEC sp_dropextendedproc 'SP _ OADestroy'
EXEC sp_dropextendedproc 'SP _ oageterrorinfo'
EXEC sp_dropextendedproc 'SP _ oagetproperties'
EXEC sp_dropextendedproc 'SP _ oamethod'
EXEC sp_dropextendedproc 'SP _ oasetproperties'
EXEC sp_dropextendedproc 'SP _ oastop'
EXEC sp_dropextendedproc 'xp _ regaddmultistring'
EXEC sp_dropextendedproc 'xp _ regdeletekey'
EXEC sp_dropextendedproc 'xp _ regdeletevalue'
EXEC sp_dropextendedproc 'xp _ regenumvalues'
EXEC sp_dropextendedproc 'xp _ regread'
EXEC sp_dropextendedproc 'xp _ regremovemultistring'
EXEC sp_dropextendedproc 'xp _ regwrite'
Drop procedure sp_makewebtask

Copy all to "SQL query analyzer"
Click -- "query" -- "execute" on the menu to delete the SQL process with security issues (the above is the technical support of genuine users of 7i24)
Change the default SA blank password. Do not use SA account for database links. Separate Account for a single database. Only public and db_owner permissions are granted.
Do not place the database in the default location.
Do not Install SQL in the PROGRAM FILE directory.
The latest SQL2000 patch is SP4.
MSSQL2000 Security Settings graphic tutorials http://www.jb51.net/article/26016.htm
Win2003 MSSQL to ordinary users running security settings http://www.jb51.net/article/23217.htm