SQL Server Registry Key Usage Tips 6

SQL Server Management is closely related to Windows Management. it is sometimes very convenient to manage SQL server through the Windows registry. I will share some of my long-term use or favorite registry skills (note: all projects are verified under Windows2003 + SQL Server2000 development edition)
Wriiten by: billpu

1. Obtain and modify SQL Server Registration:

HKEY_CURRENT_USER \ Software \ Microsoft SQL Server \ 80 \ tools \ sqlew \ registered servers x \ SQL Server Group

Each key value corresponds to the SQL Server database registry key and can be deleted directly. (Version 80 corresponds to SQL Server2000)

2. You should be familiar with changing the logon authentication method of SQL Server,
Someone on csdn often asks this question. The SA user password is also forgotten, and the login name for Windows login is removed due to security reasons. In this case, you only need to change the following registry key.

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer

Edit the loginmode value, change the original value from 1 to 2 (1 for Windows verification, 2 for hybrid verification), and restart the SQL Server service)

3. view the SQL Server version and other information

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer \ setup

Editon value: for example, Enterprise Edition is the Enterprise Edition.
Patchlevel value: version and patch number: 8.4.2039. This is actually a compound value. 8 indicates SQL Server2000, 4 indicates SP4, and 2039 indicates a small version, this is slightly different from the performance value of select @ version.
Sqldateroot value: database storage directory
Sqlpath value: sqlserver installation directory

4. Control xp_regread and xp_regwritede Permissions

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer \ extendedprocedures

Xp_regread allow paths: key value (Root) that can be read using xp_regread)
Xp_regwrite allow paths: key value (Root) that can be written using xp_regwrite)

5. query the analyzer connection history

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer \ Client \ supersocketnetlib \ lastconnect

Each key value corresponds to a historical record. I personally record all the database servers to be connected here.
In addition, the TCP Key value is the default link TCP port of the analyzer each time.

6. view the data driver allowed by SQL Server

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer \ providers

Each item here corresponds to a data driver. From the security perspective, if your application does not use so many connection methods, try to set it to 0 in the corresponding allowinprocess.