Source: http://www.xfocus.net
I. SQL Server patch version check SQL Server patch version check is not as direct, a system administrator, if you don't know the patch number of the SQL Server version, may also encounter a bit of trouble, so this explains It is a safe way to discriminate the machine by this method, and there is no impact on the system. 1. Log in to SQL Server with the ISQL or SQL query analyzer. If you use ISQL, enter ISQL -U SA in the CMD window, then enter your password, enter; if you use the SQL query analyzer, start, enter, enter SA and passwords (you can also verify using Windows). 2, enter: select @@ version; Go or SQL query analyzer input (In fact, if you don't want to enter, just open your help, you can :)) SELECT @@ version; then press execution; then return SQL version information, 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) The 8.00.760 is the version and patch number of SQL Server. The correspondence is as follows: 8.00.194 ------- SQL Server 2000 RTM 8.00.384 ------- (SP1) 8.00.534 ------ (SP2) 8.00.760 --- ---- (SP3) This way we can see the correct version and patch number of SQL Server. We can also see more detailed information with XP_MSVER. Second, the FAQ during the patch installation If you encounter the following similar error when installing the patch: 1 Follow these steps: a, restart the machine, then install, if you find that there is still this error, press step b, enter the regeditc in the start -> Run, to the hkey_local_machine / system / currentControlset / Control / Session Manager location D, Select File -> Pour, save E, right-click PENDINGFILENAMEOPERATIONS, select Delete, then confirm F, restart installation, problem solving If there is also the same problem, check if there is this value in other registry, if you have Delete.
