Shulou(Shulou.com)05/31 Report--

What are the common problems in the installation of SQL Server patches? for this problem, this article introduces the corresponding analysis and answers in detail, hoping to help more partners who want to solve this problem to find a more simple and easy way.

I. check the patch version of SQL Server

SQL Server patch version check is not as direct as Windows patch version check, a system administrator, if you do not know the patch number corresponding to the SQL Server version, may also encounter a little trouble, so here to explain, through this way to determine that the machine is a safe way, will not have any impact on the system.

1, use Isql or SQL query analyzer to log in to SQL Server, if you are using Isql, enter isql-U sa in the cmd window, and then enter the password; if you are using SQL query analyzer, please start from the program, enter sa and password (you can also use authentication).

2. Enter: in ISQL:

Select @ @ Version

Go

Or enter it in the SQL query Analyzer (in fact, if you don't want to enter, just open the help about:)

Select @ @ Version

Then press execute

The version information of SQL is returned, as follows:

Microsoft SQL Server 2000-8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)

Among them, 8.00.760 is the version and patch of SQL Server. The corresponding relationship is as follows:

8.00.194-SQL Server 2000 RTM

8.00.384-(SP1)

8.00.534-(SP2)

8.00.760-(SP3)

So we can see the correct version and patch number of SQL Server.

We can also use xp_msver to see more detailed information.

Common problems in the process of patch installation

If you encounter an error similar to the following when installing a patch:

1. During the installation process, "the pending file operation was created by the previous program, and must be restarted before running the installer". Please follow the following steps:

A, restart the machine, and then install it. If you find this error again, please follow these steps

B. Enter regedit in start-> run

C, to the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession Manager location

D. Select File-> pour out and save

Right-click PendingFileRenameOperations in the right window, select Delete, and then confirm

F, restart the installation and resolve the problem

If you have the same problem, please check whether the value exists in other registries and delete it if so.

2. When installing SQL Server SP3, sometimes a password error occurs regardless of whether you use windows authentication or mixed authentication. When you look at the sqlsp.out in the temporary directory, you will find the following description:

[TCP/IP Sockets] Specified SQL server not found.

[TCP/IP Sockets] ConnectionOpen (Connect ()).

In fact, this is a small bug of SQL Server SP3. When you install sp3, you do not listen on the tcp/ip port. You can follow the following steps:

1. Open the SQL server client network utility and server network tool, and make sure that the enabled protocol contains name pipe and is in the first place.

2. Make sure [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServerClientConnectTo]

"DSQUERY" = "DBNETLIB".

If not, please build it yourself.

3. Stop.

4. Install.

So that you can install it correctly.

This is the answer to the frequently asked questions about the installation of SQL Server patches. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.