Frequently asked questions during the inspection and installation of the SQL Server patch version

Server| Process | problems
Source: Http://www.xfocus.net

A, SQL Server patch version of the check

SQL Server patch version check is not as direct as Windows patch version check, a system administrator, if you do not understand the SQL Server version of the corresponding patch number, may also encounter a bit of trouble, so in this explanation, this way to identify the machine is a safe way, Does not have any effect on the system.
1, with isql or SQL Query Analyzer to log on to SQL Server, if it is using isql, please enter the Isql-u sa in the cmd window, enter the password, enter; If you are using SQL Query Analyzer, start from the program, enter the SA and password (or you can use Windows authentication).
2, in the isql input:
Select @ @Version;
Go

or SQL Query Analyzer input (in fact, if you do not want to enter, just open the help of the About on it:))
Select @ @Version;
followed by execution;
The version information for SQL is returned as follows:
Microsoft SQL Server 2000-8.00.760 (Intel X86) Dec 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.0 (build 2195:service Pack 3)
The 8.00.760 is the version and patch number of SQL Server. The corresponding relationship is as follows:

8.00.194-—————— SQL Server Watts 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.



Second, the patch installation process frequently asked questions


If you encounter a similar error when installing a patch:

1, during the installation process, "the previous program created a pending file operation, you must restart before running Setup," Please follow these steps to resolve:

A, restart the machine, and then install, if you find the error, please follow the steps below
b, enter regedit in the start-> run
C, to HKEY_LOCAL_MACHINE Ystem\currentcontrolset\control ession Manager Location
d, select the file-> pour out, save
E, in the right window right click PendingFileRenameOperations, select Delete, and then confirm
F, reboot installation, problem solving

If you have the same problem, please check the other registry to see if the value exists, if you delete it.


2, in the installation of SQL Server SP3, sometimes appear: regardless of using Windows Authentication or mixed authentication, all appear password error situation, then look at the temporary directory of Sqlsp.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 SQL Server SP3 bug, when installing SP3, did not listen for TCP/IP ports, you can follow these steps:

1. Open the SQL Server Client Network Utility and the Server Network tool to ensure that the enabled protocol contains name pipe and is in the first place.
2. Ensure [HKEY_LOCAL_MACHINE Oftware\microsoft\mssqlserver\client\connectto]
"DSQUERY" = "dbnetlib".
If not, please build your own
3, stop MSSQL.
4, to install.

This will allow for proper installation.