Install SQL2000 Personal Edition in Windows 7 (available, tested by myself)

Install MSDE and sqlgreemgmt separately. The former is used to install the SQL Server 2000 driver, and the latter is used to manage the SQL Server 2000 method so that SQL2000 can run perfectly.

1. Install msde2000 first
Download from Microsoft Website:
Http://download.microsoft.com/download/4/5/1/451d5d5c-69d4-40d5-b85d-f1d756cf46db/CHS_MSDE2000A.exe
Msde2000 Installation Method
1) decompress
2) enter the DOS environment/command prompt
Click "start"-"program"-"attachment"-"command prompt", and enter:
> D: the disk on which the directory is located.
> Cd/
3) enter the decompressed directory
> Cd D:/MSDE click "enter"
4) type: Setup sapwd = "sa" securitymode = SQL disablenetworkprotocols = 0 and press Enter.
The sapwd parameter refers to the SA password, which is used in the "administrator password" of the "Install Database" step of Excel server 2006. You can set it by yourself.

In this way, msde2000 is installed! The SQL2000 instance has been installed.

2. Install SQL2000 directly (because the instance has been installed, you can modify or uninstall the installation and install the management tool/other .......)

3. Patch SP4

However, after the installation process, you cannot install the SQL SP4 patch. An error occurs after a dozen times, or the logon permission is insufficient. After the MSSQLServer logon permission is set in the service, you cannot patch and start the SQL Service normally.

The above method should not be a big mistake, because I used the green version of sqlgreemgmt, which can be used normally, and can also start the service, Enterprise Manager, and query analyzer. But it still cannot be patched with SP4. So I deleted it.

In desperation, I uninstalled the self-installed SQL Server (according to the method described at above) and installed it again. Instead, I chose a new instance for installation. All the way down, next, SP4 patch, no problem. Strange!

The Enterprise Manager is in normal use, the service is started, the database is attached, and the software connection is normal. The query analyzer connection is also normal. A little bit. You don't have the intention of planting flowers and flowers.

Currently, only one problem is found. You cannot create a new table in the database, and MMC will exit. Other operations are normal, but adding fields is correct. Therefore, I use the SQL statement in the query Analyzer:
Creat table name (id int)

In this way, a table is created, and the table passes through normally. Refresh and view the table normally. Then, modify the field name or add a field. Everything works normally. No compatibility issues will be prompted when you enable it.

Conclusion: The above methods or the methods I accidentally found can work, and MSDE installation is the key.