Hot Fix 826161

After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server t
hat has the security patch MS-031 installed, the version number remains at 8
.00.818. Is it supposed to change to 8.00.819?
Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described for
SQL 2000.The build number in the filename of the patch is not necessarily the level
that the file patches sqlservr.exe to... if you re-read the article, it
clearly shows that sqlservr.exe becomes 2000.80.818.0 ... this is what
@.@.VERSION returns.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"RC5640808" <anonymous@.discussions.microsoft.com> wrote in message
news:AF037BF8-210D-40D6-A797-8C783AF17425@.microsoft.com...
> After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server
that has the security patch MS-031 installed, the version number remains at
8.00.818. Is it supposed to change to 8.00.819?
> Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described
for SQL 2000.
>|||Hi
As this fix does not contain a new version of SQLServr.exe the version
number will not change. The hotfix for machines that do not have MS-031 does
have a version of the file which is labelled 818. I am not sure about SQL
Server 7.
John
"RC5640808" <anonymous@.discussions.microsoft.com> wrote in message
news:AF037BF8-210D-40D6-A797-8C783AF17425@.microsoft.com...
> After applied this hot fix (SQL2000Tools-KB826161-8.00.0819) on the server
that has the security patch MS-031 installed, the version number remains at
8.00.818. Is it supposed to change to 8.00.819?
> Do we have the hot fix for SQL 7? Same problem in SQL 7 as it described
for SQL 2000.
>|||I found that once this hot fix is applied, it also fixes the problem for SQL
7.
I think probably is only a bug in the EM and only one copy of EM for the ser
ver that has both SQL 7 and 2000 instances.
Thanks.|||This is correct. The problem is in Enterprise Manager for SQL Server 2000.
It does not affect SQL Server 2000 or SQL Server 7.0 from the server side,
on ly the client side. This is why the problem does not occur for SQL
Server 7.0 after you applied the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.