Hotfix Post SP4

Hi all,
I am searching for a list of published hotfix posted after SQL Server SP4.
Is there such a link or URL, on the Microsoft site?
Thank you for your time.
Franco
Nope. You kind of have to poke around. There are 3 post-SP4 hotfixes that
I am aware of:
Build 2040, to fix the AWE memory issue.
Build 2148, to fix the SQLDiag issue, but also fixes another 10 or so.
Build 2151, to fix the Query Analyzer DTC issue.
This site can be helpful though.
SQL Server Version Database
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
Otherwise, you are stuck searching through the Microsoft Support site.
Build 2040:
FIX: Not all memory is available when AWE is enabled on a computer that is
running a 32-bit version of SQL Server 2000 SP4
http://support.microsoft.com/default...b;en-us;899761
Build 2148:
FIX: An access violation may occur when a deadlock graph is written to the
error log in SQL Server 2000
http://support.microsoft.com/default...b;en-us;898626
FIX: An access violation may occur when you run a SELECT query and the
NO_BROWSETABLE option is set to ON in Microsoft SQL Server 2000
http://support.microsoft.com/default...b;en-us;899430
FIX: An access violation occurs in the Mssdi98.dll file, and SQL Server
crashes when you use SQL Query Analyzer to debug a stored procedure in SQL
Server 2000 Service Pack 4
http://support.microsoft.com/default...b;en-us;899431
FIX: The Mssdmn.exe process may use lots of CPU capacity when you perform a
SQL Server 2000 full text search of Office Word documents
http://support.microsoft.com/default...b;en-us;900390
FIX: The results of the query may be returned much slower than you expect
when you run a query that includes a GROUP BY statement in SQL Server 2000
http://support.microsoft.com/default...b;en-us;900404
FIX: You receive a "Failed to open a table" error message when you try to
open a trace table by using SQL Profiler after you upgrade to SQL Server
2000 Service Pack 4
http://support.microsoft.com/default...b;en-us;900629
FIX: You may receive a "Server: Msg 7358, Level 16, State 1, Line 1" error
message after you run a linked server query in SQL Server 2000 Service Pack
4
http://support.microsoft.com/default...b;en-us;901200
FIX: You receive an error message if you use the sp_addalias or sp_dropalias
procedures when the IMPLICIT_TRANSACTIONS option is set to ON in SQL Server
2000 SP4
http://support.microsoft.com/default...b;en-us;901212
FIX: Some 32-bit applications that use SQL-DMO and SQL-VDI APIs may stop
working after you install SQL Server 2000 Service Pack 4 on an Itanium-based
computer
http://support.microsoft.com/default...b;en-us;902150
FIX: You receive a "Getting registry information" message when you run the
Sqldiag.exe utility after you install SQL Server 2000 SP4
http://support.microsoft.com/default...b;en-us;902955
FIX: The batch job stops running, and job output is truncated when you run a
Transact-SQL script as a SQL Server Agent job in SQL Server 2000
http://support.microsoft.com/default...b;en-us;903086
Build 2151:
FIX: You receive an "Error: 8526, Severity: 16, State: 2" error message in
SQL Profiler when you use SQL Query Analyzer to start or to enlist into a
distributed transaction after you have installed SQL Server 2000 SP4
http://support.microsoft.com/default...b;en-us;903742
Sincerely,
Anthony Thomas

"Franco" <Franco@.discussions.microsoft.com> wrote in message
news:6C7551B7-1250-4504-B844-D81BCCDEF252@.microsoft.com...
> Hi all,
> I am searching for a list of published hotfix posted after SQL Server SP4.
> Is there such a link or URL, on the Microsoft site?
> Thank you for your time.
> --
> Franco
|||Thank you very much.
I really appreciate your answer.
Kind regards.
Franco
"Anthony Thomas" wrote:

> Nope. You kind of have to poke around. There are 3 post-SP4 hotfixes that
> I am aware of:
> Build 2040, to fix the AWE memory issue.
> Build 2148, to fix the SQLDiag issue, but also fixes another 10 or so.
> Build 2151, to fix the Query Analyzer DTC issue.
> This site can be helpful though.
>
> SQL Server Version Database
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37
>
> Otherwise, you are stuck searching through the Microsoft Support site.
>
> Build 2040:
> FIX: Not all memory is available when AWE is enabled on a computer that is
> running a 32-bit version of SQL Server 2000 SP4
> http://support.microsoft.com/default...b;en-us;899761
>
> Build 2148:
> FIX: An access violation may occur when a deadlock graph is written to the
> error log in SQL Server 2000
> http://support.microsoft.com/default...b;en-us;898626
> FIX: An access violation may occur when you run a SELECT query and the
> NO_BROWSETABLE option is set to ON in Microsoft SQL Server 2000
> http://support.microsoft.com/default...b;en-us;899430
> FIX: An access violation occurs in the Mssdi98.dll file, and SQL Server
> crashes when you use SQL Query Analyzer to debug a stored procedure in SQL
> Server 2000 Service Pack 4
> http://support.microsoft.com/default...b;en-us;899431
> FIX: The Mssdmn.exe process may use lots of CPU capacity when you perform a
> SQL Server 2000 full text search of Office Word documents
> http://support.microsoft.com/default...b;en-us;900390
> FIX: The results of the query may be returned much slower than you expect
> when you run a query that includes a GROUP BY statement in SQL Server 2000
> http://support.microsoft.com/default...b;en-us;900404
> FIX: You receive a "Failed to open a table" error message when you try to
> open a trace table by using SQL Profiler after you upgrade to SQL Server
> 2000 Service Pack 4
> http://support.microsoft.com/default...b;en-us;900629
> FIX: You may receive a "Server: Msg 7358, Level 16, State 1, Line 1" error
> message after you run a linked server query in SQL Server 2000 Service Pack
> 4
> http://support.microsoft.com/default...b;en-us;901200
> FIX: You receive an error message if you use the sp_addalias or sp_dropalias
> procedures when the IMPLICIT_TRANSACTIONS option is set to ON in SQL Server
> 2000 SP4
> http://support.microsoft.com/default...b;en-us;901212
> FIX: Some 32-bit applications that use SQL-DMO and SQL-VDI APIs may stop
> working after you install SQL Server 2000 Service Pack 4 on an Itanium-based
> computer
> http://support.microsoft.com/default...b;en-us;902150
> FIX: You receive a "Getting registry information" message when you run the
> Sqldiag.exe utility after you install SQL Server 2000 SP4
> http://support.microsoft.com/default...b;en-us;902955
> FIX: The batch job stops running, and job output is truncated when you run a
> Transact-SQL script as a SQL Server Agent job in SQL Server 2000
> http://support.microsoft.com/default...b;en-us;903086
>
> Build 2151:
> FIX: You receive an "Error: 8526, Severity: 16, State: 2" error message in
> SQL Profiler when you use SQL Query Analyzer to start or to enlist into a
> distributed transaction after you have installed SQL Server 2000 SP4
> http://support.microsoft.com/default...b;en-us;903742
>
> Sincerely,
>
> Anthony Thomas
>
> --
> "Franco" <Franco@.discussions.microsoft.com> wrote in message
> news:6C7551B7-1250-4504-B844-D81BCCDEF252@.microsoft.com...
>
>