Difference in concurrency performance between sqlserver 2000 Personal Edition and Enterprise Edition

Recently, an internal management system of the company frequently experienced problems. The backend of the system used SQL Server 2000.
When 20 concurrent accesses are made, some of them are delayed for more than 10 minutes, and the final timeout occurs. When the server is accessed by 20 concurrent users,
CPU, memory, hard disk, network and other indicators are normal, so it is not a problem caused by hardware performance.
After a variety of tests failed, occasionally in the Application Program "Sqlserver Personal Edition" is found in the log,
Check whether the performance problem is caused by the sqlserver Personal Edition. Because the internal management system is
Company (using sqlserver2000 Enterprise Edition) has been in use for several years. When concurrency is 100 or 200, the latency cannot exceed a few
Seconds.
Microsoft said that sqlserver2000 Personal Edition imposes performance restrictions on more than five concurrent users.
Select @ version to confirm that the server uses the Personal Edition. The next step is to reinstall it.
First, an error occurred while installing the Enterprise Edition. After some Google operations
Problem: it is OK to clear the old sqlserver when installing sqlserver for the second time. steps:
1. Delete the sqlserver2000 installation directory
2. Delete the registry key:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer
HKEY_CURRENT_USER \ Software \ Microsoft \ microsoft sqlserver

Next, attach the detached database to the newly installed sqlserver 2000. Isolated users.
For example, the table in the old database is created by the user test. After the database is appended, the user test becomes an orphan.
Login User, there is no corresponding login user name, even if you create a new test login user name, and is a previous
User Password. The user table that previously belonged to test cannot be operated after logon with this user. Because it is used in the system
Sid to identify the user. The new and old test users have different Sid, so the above problem occurs.
The solution is to use the Stored Procedure sp_change_users_login
Test, an isolated user of the database, corresponds:
Sp_change_users_login has three actions: Report, update_one, and auto_fix.
Sp_change_users_login 'report'
List isolated users of the current database
Sp_change_users_login 'Update _ one', 'test', 'test'
Match the old test user with the new test Login User
You can also use
Sp_change_users_login 'Auto _ fix', 'test', null, 'testpassword'
Create a login user test with the password testpassword. Add the old test user and the new
Test Login User