MSSQL security Settings for server security Settings

MSSQL security Settings, will have security problems SQL process to remove. More comprehensive.1 cut for security!
Removed corrupt permissions to invoke shell, registry, COM components

 
use master 
EXEC sp_dropextendedproc 'xp_cmdshell' 
EXEC sp_dropextendedproc 'Sp_OACreate' 
EXEC sp_dropextendedproc 'Sp_OADestroy' 
EXEC sp_dropextendedproc 'Sp_OAGetErrorInfo' 
EXEC sp_dropextendedproc 'Sp_OAGetProperty' 
EXEC sp_dropextendedproc 'Sp_OAMethod' 
EXEC sp_dropextendedproc 'Sp_OASetProperty' 
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, and the security problem will be removed from the SQL process.
Change the default SA empty password. Do not use an SA account for database links. Set up a separate use account for a single database. Give public and db_owner permission only.
Do not place the database in the default location.
Do not install SQL under the PROGRAM FILE directory.
The most recent SQL2000 patch is SP4
MSSQL2000 security Settings by tutorial / / www ofstack. com article / 26016. htm
Win2003 MSSQL with ordinary users running security Settings / / www ofstack. com article / 23217. htm