How to install SQL2000 Enterprise Edition in Windows XP

The SQL2000 Enterprise Edition is applicable to Windows 2000 & NT & 2003 systems. You do not need to use a Personal Edition for XP installation. Here we will introduce a method for installing SQL2000 Enterprise Edition under XP for your reference ~ The method is as follows: In the installation disk of the SQL Server, find the msdedirectory and click setup.exe to install it. The process is simple and the next step is OK. 2. restart Windows XP and the SQL Service icon appears. 3. Take out the installation CD of the SQL Server version and install the client tool directly? The simplest example is to directly click autorun.exe under the optical disk root directory) Install the tool as prompted. If you know that the system is not a server version during the self-check process, you will be prompted to only install the client tool. (Haha, I already have the server) 4. Open the Enterprise Manager and try connecting the SA user to see if the SA User Login fails? Because you have not been associated with a trusted SQL server connection. Fortunately, you only need to slightly modify the system registry: Enter Regedit in the running directory to open the Registry Editor and find [HKEY_LOCAL_MACHINE // software // Microsoft // MSSQLServer ]. There is a key value loginmode. By default, the value is 1. Change the value to 2 and restart the computer. 5. Start enterprise management and try again. OK! In addition, because I am in the 4in1 version, I found other items for my reference. If you download the four-in-one installation file, there is a total of four versions of the Installation File: Personal Edition, Enterprise Edition, Standard Edition, and development edition. For the first installation, follow these steps: Step 1: In the sqlserver installation disc, find the msdesub-directory under the enterprise, and click setup.exe to install it. The process is simple and the next step is OK. Step 2: restart the computer. You can skip this step, but we can verify whether the server has been installed. If the icon of the SQL Service appears after it is started, congratulations! We have installed it on the server of the Enterprise Edition .. If not, repeat Step 1! Step 3: Run autorun.exe on the installation disc, select Enterprise Edition, and click Next. Install as prompted. If you know that the system is not Server Edition during the self-check process, you will be prompted to only install the client tool. Don't worry about him. We have installed all our servers ~ Continue to the next step. During this process, an error message is displayed: (a previously installed program has created a suspended file on the installation computer. Restart the computer before running the installer .) That is, the problem I mentioned above. Click OK and then open "run" => Regedit => open registry editor in the Start Menu, find the pendingfilerenameoperations project in HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/Session Manager and delete it. In this way, you can clear the temporary installation project. Let's go back to the installation page and click Next ~ Step 4: After the installation is complete, open the registry, find the HKEY_LOCAL_MACHINE/software/Microsoft/MSSQLServer item, and change the value of loginmode to 2. Please note that you should not find the wrong location, because I saw the error at the beginning and did not find the loginmode item for a long time, I started looking for HKEY_LOCAL_MACHINE/software/Microsoft/microsoftsql server. Oh, careless ~ Step 5: if the service manager is missing from the "installation completion" menu, create a shortcut for the following program: C:/program files/Microsoft sqlserver/80/tools/binn/sqlmangr.exe Step 6: Open the Enterprise Manager and expand the (local) instance. If the instance cannot be connected, delete it. The account SA password for creating a (local) connection is blank. After the connection is successful, it is best to change the password, expand the sqlserver instance, and choose security> logon> Sa> Properties> password. Possible problems: 1. After the installation is complete, fewer database pubs and so on. This is only the database used by the sample program and can be imported from other machines. 2. Check whether the MSSQLServer and SQLServerAgent services are enabled. 3. In fact, the installation is not a real Enterprise Edition, but SQL Server2000 is installed under XP using sqlserver2000 of the Enterprise Edition. I think everyone has had a failure to install the SQL Server 2000 database in Windows XP. Because SQL Server2000 is installed only on the server version by default, you cannot install SQL Server2000 in your home version. If you have accessed the Internet to find a helper for installing SQL Server, click setup.exe to Install SQL server in the msde directory under the optical drive, and then reinstall the server version from the optical drive autorun.exe file. But in the Windows XP SP2 version of Tomato Garden (in fact, I don't like the XP version of tomato garden, but I just don't want to re-set and install new patches, just like her skin, lazy ~ :) In addition, XP has another problem, such as 2000 or 2003 convenience, which is too troublesome sometimes .) The related methods are useless at all. It is estimated that many people will encounter such a situation. When you click autorun.exe, the system does not prompt "You cannot install the server, you can only install the client". Instead, you can install the server in the same way as 2000 or 2003. But when you select to install the database type, the following message appears: "A previous program has been installed to create a suspended file on the installation computer. You must restart the computer before running the installer. What should I do? Do you have to change the version if it is not installed? I like this person, no matter what you are, as long as it is what I want, that is, your search engine contains one hundred websites, I also want to see them one by one, until it is found. Huang Tian has no worries. I have found a solution to this problem. Open the Registry Editor and go Pendingfilerenameoperations is found in HKEY_LOCAL_MACHINE/system/CurrentControlSet/control/Session Manager. Project, and delete it. In this way, you can clear the temporary installation project. Please open your SQL Server2000 installation disk and go straight. An exciting scene is displayed. SQL Server2000 is successfully installed! (I won't talk about the steps ). If the deleted registry does not take effect, perform the following operations: 1. Start/run/Enter regedit and press ENTER + HKEY_LOCAL_MACHINE + System + CurrentControlSet + Control + Delete filerenameoperations under Session Manager Ii. + HKEY_LOCAL_MACHINE + Software + Microsoft + Windows + CurrentVersion + Setup + Delete all the items under predictioncomponents, for example: {077acec7-979c-40ab-9835-435ba1511e0d} {30c7234b-6482-4a55-a11d-ecd9030313f2} {3fdf25ee-e592-4495-8391-6e9c504dac2b} {60204bb3-7078-4f70-8f69-68297621941c }...... In short, if there are several items, delete them, delete them, restart them, and then Install SQL Server, there will be no hint. Delete MSSQL related items in the Registry and the system. ========================================================== ==== Install SQL2000 Enterprise Edition for XP Yingmd was published on 1:04:00 The SQL2000 Enterprise Edition is applicable to Windows 2000, and the 2003 and XP systems generally cannot be installed with the individual edition. Of course, if you have worked hard to download the Enterprise Edition, you cannot install it, are you disappointed? This document describes how to install SQL2000 Enterprise Edition in XP for your reference ~ The method is as follows: The installation process is simple and the next step is OK. 2. restart Windows XP and the SQL Service icon appears. 3. Take out the installation CD of the SQL Server version and install the client tool directly? The simplest example is to directly click autorun.exe under the optical disk root directory) Install the tool as prompted. If you know that the system is not a server version during the self-check process, you will be prompted to only install the client tool. (Haha, I already have the server) 4. Open the Enterprise Manager and try connecting the SA user to see if the SA User Login fails? Because you have not been associated with a trusted SQL server connection. Fortunately, you only need to slightly modify the system registry: Enter Regedit in the running directory to open the Registry Editor and find [HKEY_LOCAL_MACHINE/software/Microsoft/MSSQLServer ]. There is a key value loginmode. By default, the value is 1. Change the value to 2 and restart the computer. If the method above does not allow SA to log on normally, you can use Windows authentication to log on. Then, change the SA password to sa. 5. Start enterprise management and try again. Is it OK! ============ 1. When installing SQL Server 2000, the system prompts: "another instance is running and cannot be installed" Note: This is generally because SQL Server 2000 has been installed before (this is the case even if it is not correctly installed before). During re-installation, some processes are not completed, or the registration information already exists. First, restart the computer. If the installation is still unavailable after the restart (delete the files related to the SQL installation directory as much as possible and pay attention to the protection of important data), select "run" from the Start Menu, enter Regedit to go to the Registry Editor and find Microsoft SQL Server2000 in hkey_lccal_machine/software/Microsoft/Windows/CurrentVersion/uninstall registration information. Right-click to delete it and you will be able to install it again. 2. When installing SQL Server 2000, the following error message is displayed: "A previously installed program has created a suspended file on the installation computer. You must restart the computer before running the installation program" Note: If the problem cannot be solved after the computer is restarted, there may be two reasons: A. the involved file is marked as read-only or the user does not have full control permissions; check the following registry subkeys: HKEY-LOCAL-MACHINE/system/CurrentControlSet/control/Session Manager, find pendingfilerenameoperations, check whether the involved physical files are marked as read-only or the user does not have full control permissions. If yes, you must cancel the read-only attribute and grant the user full control permissions. B. You do not have full control over the involved registry subkeys: you must use the Regedit command to enter the Registry Editor and grant users full control over this registry subkey. If the problem persists, You can manually delete the pendingfilerenameoperations subkey.