SQL Installation Problems

SQL Installation Problems

Sql2005 installation problem summary
Sql2005 is divided into five versions, as listed below,
　　1. Enterprise (Enterprise Edition ),
2. Development (Development edition ),
　　3. Workgroup, (Work Group version)
　　4. Standard, (standard)
　　5. Express. (well, I guess it's a simple version)
Which of the following versions should we use ﹖
This is the most frequently asked question for many beginners of sql2005.
Let me briefly compare the three editions of enterprise, development, and express: in terms of functions, enterprise and development have the same functions. The differences between the two are:
Enterprise database engines can only be installed on win2003server (or other servers ).
If you want to install Windows XP Pro, you should install sql2005development (Development edition ).
Note: Someone asked what is "Database Engine 」. Well, the database engine is the core of sql2005 and the main functional module of database management. Without it, it is not a database management system.
Many people download sql2005express because it is free and can be downloaded directly from the Microsoft website. However, apart from supporting a relatively small amount of memory, the most important thing is
It lacks the "Enterprise Manager" and "query analyzer" equivalent to SQL2000 」.
Note: "Enterprise Manager" and "query analyzer" under SQL2000 have been combined into one in sql2005 and are called management studio.
Therefore, if you are a beginner and want to learn at home, if your environment is Windows XP Pro, you should choose sql2005development (Development edition ), instead of sql2005enterprise (Enterprise Edition) or sql2005express (simple edition ).
Sql2005 publisher, are you correct?

"Microsoft. SQL. server.2005. Enterprise. Edition. DVD-zwtiso, please download acceleration"
The description file is displayed as "Standard Edition and Enterprise Edition", but I cannot meet the minimum hardware requirements during installation (my machine configuration: server2003 Enterprise Edition amd2800 +, 512 M ddr400 memory, with 16 GB free space on the system disk). In the component selection box, you can only see native client and install the sample database. Why? Is the hardware requirement of 2005 so high? Or does this affect installation and use?
How can I solve the above problems without changing the hardware? It should meet the hardware requirements. Let's see what the prompt is during installation. 2005 database installation experience

My environment is XP SP2 en, SQL2005Dev, memory 512 MB.
First of all, my system has been used for more than half a year. It has installed vs2003, SQL2000, netframework2.0beta, and several beta versions of SQL.2005It is very "dirty. At the earliest time, I went to a 2005ee version and couldn't install it. Later I found that EE didn't support XP =_=, and then I went to the De version.

At the beginning of installation, I was shocked, and yarn took more than 1300 MB of my C drive !! Sorry. (I installed SQL on the F disk, but I still need more than 1300 MB of the C disk ). But the installation failed. I read the Installation Log, but I don't understand it. Only the native client components cannot be installed successfully. Repeated issues remain.

After studying the installation package, we found that there are two main folders: Server and tools. As the name suggests, the server must be a service installation file, and the tools should be the installation files of those tool components. In tools, there was a setup, and the installation was successful, and only occupied more than 200 MB of my C drive. I was so excited (I didn't choose Bi, that is, the business intelligence component, too large ). Then restart the computer (not required, but the system is too slow after setup) and enter the server directory. Of course, there is also a setup to run, it is actually used to install the service. The installation was successful this time. I went back to disk C. Haha, I used more than 300 MB in total, saving 1 GB.

Of course, if you install the SDK together, you may not need to use up MB of space, because some junk files will be automatically deleted after the installation is complete. But in any case, at least let me install it normally. My c drive only has 1400 free space. I don't know if it is related to the initial installation failure.

So far, SQL 2005 has successfully settled on my computer. During installation, if your computer is out of memory (less than 1 GB) like mine, and the performance is insufficient (My CPU is centrio1. 3g, huh, it is installed on the local file). We recommend that you choose not to choose the services that need to be run when installing the system, and then run them manually.

Run management studio. Well, the speed is quite fast. There is no localhost to connect to the server. In this case, Open Server Configuration Manager and run the MSSQLServer on the right. OK. No problem this time.

If everything works properly, we find that the database backed up from SQL2000 can only modify data through SQL statements under MySQL 2005, but cannot see or make any changes. I don't know what's going on.

BTW: Later I installed the business intelligence component. I only used the C drive for 150 MB. Warning for COM + directory problems during sql2005 Installation

The installation of sql2005 failed. I thought the problem was caused by the COM + directory Issue warning. I found a solution to this problem for a long time.
Experience in installation failure of sql2005_std_x86 on XP SP2
The soft environment is XP SP2, and sql2005_std_x86 is installed.
Fault prompt:
1. If the SQL Server installation fails, the installer rolls back the installed system, but may not delete all. manifest files. The solution is to rename these files and run the installer again. For more information, see "how to handle the failure of COM + check during SQL Server Installation ". If Microsoft Distributed Transaction Coordinator (ms dtc) is not running, or if ms dtc is not a cluster resource when Microsoft Cluster Server is used, a COM + error may occur. COM + depends on ms dtc, while Message Queue tasks in integration services depend on COM +. If a COM + error occurs, the Message Queue task in integration services is available only after the COM + system is correctly configured.
2. An error occurred while performing the System Configuration check on the registry value of the performance monitor counter. For more information, see "how2005Add the counter registry key value for the installer ".
The installation is aborted.
Find the books online with the following prompt:
1. Microsoft SQL Server2005The installer checks whether COM + is correctly configured. If a configuration error is found, the installer continues, but the following warning is displayed in the System Configuration check (SCC) report:
"If the SQL Server installation fails, the installation will roll back the installation, but may not delete all. manifest files. The solution is to rename these files and run the installer again ."
If Microsoft Distributed Transaction Coordinator (ms dtc) is not running, or if ms dtc is not a cluster resource when Microsoft Cluster Server is used, a COM + error may occur. COM + depends on ms dtc, while Message Queue tasks in integration services depend on COM +. If a COM + error occurs, the Message Queue task in integration services is available only after the COM + system is correctly configured.
To use a Message Queue (also known as MSMQ), make sure that the ms dtc is running and configured correctly. If SQL Server is installed on a cluster, MS DTC must be a cluster resource.
Reinstall COM + as follows.
Install Component Service Management Unit
On the Windows desktop, click Start and then click Run ".
In the open box, type MMC and click OK ".
In the "console" window, click "Files" on the menu bar, and then click "Add/delete snap-in ".
In the Add/delete snap-in window, click Add ".
In the "add independent management unit" window, select "component service" from the management unit list, and click "add ".
Click Close to close the add independent unit window, and then click OK to close the Add/delete unit window.
In the "Console Root Node \ component service" window, expand the "component service" tree. This is where the error message may occur when a problem occurs with COM +.
Run SQL server again2005Installation program. If you receive an error message, reinstall COM +.
Reinstall COM +
From add or delete programs on the control panel, click Add/delete Windows Components ".
In the "Windows component wizard", if you do not make any changes to the selection, click "Next ".
Always click to complete the wizard, and then run SQL server again2005Installation program.
2. Before SQL Server Installation starts, the installation configuration Checker (SCC) in the Microsoft SQL Server Installation Program verifies the value of the counter registry key. If the SCC cannot verify the existing registry key, or the SCC cannot run the lodctr.exe system program, the SCC check fails and the installation is blocked.
Incorrect registry editing can seriously damage your system. Before changing the registry key, we recommend that you back up all important data on your computer.
Manually set the increment of the counter registry key
In Microsoft Windows2003Or on the Windows XP desktop, click Start and run, type regedit.exe in open, and then click OK ". In Windows2000, Use regedt32.exe to start the Registry Editor.
Go to the following registry key:
[HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Perflib]
"Last counter" = DWORD: 00000ed4 (5276)
"Lasthelp" = DWORD: 00000ed5 (5277)
The value of "Last counter" in the previous step (5276Must be associated with "Perflib \" in the following registry key \009", And the" last help "value in the previous step (5277Must be associated with "Perflib \" in the following registry key \009.
[HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Perflib \ 009]
Note:009Is an example in English. The values of "Last counter" and "last help" are dynamically allocated by windows. These two values vary depending on the computer.
If necessary, modify the values of "Last counter" and "last help" in "\ Perflib": In the right pane, right-click "Last counter" or "last help", click "modify", then click "base =" decimal ", and set the value in" value data, click OK ". Repeat the above process for another item if necessary, and then close the registry editor.
Run the SQL Server Installation program again.
Solution Process:
The COM + check fails, not to mention whether the component in the component message queue is not installed or the service is not started. No message queue is installed on the local machine. Find out the system disk and install the Message Queue component. When the component is installed, the system prompts that the MSDTC service has not been started. This process takes a long time, why can't mstdc be found in the service? I thought about whether it would be DTC (the mind is a bit dumb, but I should think of it from the name of MSMQ ), it turns out that there is Distributed Transaction Coordinator (DTC), but this service cannot be started. Later, find the relevant information: the MSDTC (Distributed Transaction Coordinator) service must run under the nt authority \ NetworkService account; even nt authority \ Network Service (note that there is a space between the network and service) does not work (as for the differences between the two accounts, it is not found on the Internet, but I hope you will not give me any further ). If the Logon account is changed, the MSDTC Service continues to run, but an error may occur during execution. In addition, the following error information can be found in the "application" of the event log:
The account that is running the ms dtc service is invalid. This happens if the service account information is changed using the service snap-in the Microsoft Management Console (MMC. The ms dtc service will continue to start. Confirm that ms dtc service account information is updated using component service manager.
To change to a correct Logon account, we can:
Find the Distributed Transaction Coordinator service in the service and select "properties ";
On the "Logon" tab, select "this account" and enter "nt authority \ NetworkService" in the account name. The password is blank;
Click "OK" and restart the service.
Alternatively, run MSDTC-uninstall on the command line to uninstall the MSDTC Service;
Run MSDTC-install to install the MSDTC Service.
The mstdc service is successfully started, and the "COM + application" in the component service can be accessed. The above 2nd faults have not been solved. First, try to install them to see if there are any errors. It is surprising that the installation check is successful, 2nd errors are also fixed.
Of course, the process of solving the problem is also different from that of the system environment. Here we will talk about the small setbacks of my installation and hope to give some tips to those who encounter the same problem. Owc11 error handling during sql2005 Installation

Sql2005, which has been installed for a long time recently, has encountered many problems during the process. The previous COM + directory warning is a part. After processing it, I still find that the installation has never been successful, (For this reason, I have installed more than 10 times) to solve the problem.
The following errors are found during installation
Product: owc11
Error: Error1706. The installer cannot find the required file. Check the network connection or CD-ROM drive status. For other possible solutions to this problem, see c: \ Program Files \ Microsoft Office \ office11 \2052\ Setup. CHM.
--------------------------------------------------------------------------------
I found that my ocw11 was not installed, and all the related components on the server could not be installed,
In Microsoft ocw11
Find Microsoft's ocw11, select Simplified Chinese, download and install, and find that the same problem still occurs,
Decompress the downloaded ocw11 file and observe the ocw11.xml file. It is found that the setup directory of the SQL 2005 server contains the same file name, after comparison, we found that all the files in the file package in the ocw11 had corresponding setup, but we found that the two CHM suffixes were different. One was 10xx, and the other was 2052, the original version is different.
Directly run Setup in the setup directory, select a file source that is fixed or completely installed, and copy all the corresponding ocw11 files under the setup directory to the hard disk, after running and repairing the problem again, sql2005 was successfully installed. The problem that plagued me for two days was finally solved. I would like to share this article with all my friends who studied sql2005. I hope you can avoid any detours. exchange SQL functions together