SQL Server Security System Improvement

To make the database more capable of resisting attacks, you must take several steps. Some measures are only part of good server management, such as having the latest patches for SQL Server, and others include in-use user supervision. The following are five steps:

Query the latest service package

Make sure that you always have the latest service package. For SQL Server2000, this is sp3a. Remember that there are multiple service packages. If you use sp3a, you do not have to use the previous service packages, such as SP3, SP2, or SP1. SP3 is a special service package. Once installed, it will no longer use any previous upgrades.ProgramBut it requires that SP1 or SP2 have been installed.

Register Security Alerts

Although the service package helps your SQL Server database avoid many threats, they are not able to cope with security issues such as attackers and worms. You need to register Microsoft's free security notification service, which will notify you via email about what has penetrated your security system and how to solve them.

Run Microsoft Baseline Security Analyzer (mbsa)

This tool targets SQL Server and msde2000 desktop engines. It can be used locally or online. It uses password, access permission, access control list, registration, and other methods to find problems, and it finds the lost security package or service package. You can find related information on technet.

Delete SA and old password

A common security error is that you do not change the system management password. You will easily ignore the installation files and remaining configuration information, without well-protected authentication information and other sensitive data, which may be attacked. You must delete the old Installation File: Program filesmicrosoft SQL servermssqlinstall or program filesmicrosoft SQL severmssqlinstall or program files Microsoft SQL servermssql $ install folders. similarly, use the killpwd tool to find the old passwords and delete them.

Monitoring connection

The connection tells you who is attempting to access SQL Server. Therefore, monitoring connection is a good way to ensure database security. For a large running SQL Server, too many link data may need to be monitored. However, it is necessary to monitor the failed links because they may represent some attempts. You can log on to the enterprise manager with the failed links. 1. Right-click the server and select Properties ). 2. Click the Security tab and select failure under audit level. 3. Stop and restart the server to get the start of the check.