SQL Server patch installation FAQs

I. Check the patch version of SQL Server

The patch version check of SQL Server is not as direct as the windows patch version check. If a System Administrator does not know the patch number corresponding to the SQL Server version, it may also encounter some trouble, therefore, it is explained that using this method to identify machines is a safe way and will not affect the system.

1. log on to SQL Server using iSQL or SQL query analyzer. If iSQL is used, enter iSQL-U sa in the CMD window, and then enter the password; if you use the SQL query analyzer, start it from the program and enter the SA and password (you can also use Windows for verification ).

2. in iSQL, enter:

Select @ version;
Go

Or input in the SQL query analyzer (in fact, if you don't want to enter it, you just need to open the help information :))

Select @ version;

Then, press the execution button;
The SQL version information 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)

8.00.760 indicates the SQL Server version and patch number. The relationship is as follows:

8.00.194 ------- SQL Server 2000 RTM
8.00.384 ------- (SP1)
8.00.534 ------- (SP2)
8.00.760 ------- (SP3)

In this way, we can see the correct version and patch number of SQL Server.
We can also use xp_msver to see more detailed information.

Ii. FAQs during patch installation

If the following error occurs during patch installation:

1. During the installation process, the following steps show:

A. Restart the machine and install it again. If the error persists, follow these steps:
B. Enter Regedit in start-> running
C. Go to the HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager location
D. Select File-> inverted, save
E. Right-click pendingfilerenameoperations in the right window, select Delete, and then confirm
F. Restart the installation and solve the problem.

If the problem persists, check whether the value exists in other registries. If yes, delete it.

2. When installing SQL Server SP3, sometimes there will be a Password error in both Windows Authentication and Hybrid Authentication. In this case, check the sqlsp in the temporary directory. out, 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 in SQL Server SP3. When installing SP3, you do not listen to the TCP/IP Port. You can follow these steps:

1. Enable the SQL Server Client Network utility and server network tool to ensure that the enabled protocol contains name pipe, which is placed first.
2. Ensure that [HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer \ Client \ connectto]

"Dsquery" = "dbnetlib ".
If not, create your own

3. Stop MSSQL.
4. Install the SDK.

In this way, you can install it correctly.