Article ID: 900629 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 474402 (SQL Server 8.0)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release.
This article describes the following about this hotfix release:
After you install Microsoft SQL Server 2000 Service Pack 4 (SP4), you receive the following error message when you try to open a trace table by using SQL Profiler:
Note To save a SQL Profiler trace file to a table, use the fn_trace_gettable function to read from the SQL Profiler trace file.
Failed to open a table.
For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/810185/ )SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
This problem occurs because SQL Profiler cannot read the trace table. For example, this problem occurs if the table schema is not correct.
In SQL Server 2000 SP4, a code change was made to sort the table contents according to the RowNumber column. The RowNumber column is automatically created when you create a trace table by using SQL Profiler.
However, the RowNumber column is not created in the trace table if the following conditions are true, in the order in which they are presented:
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must have SQL Server 2000 SP4 installed to apply this hotfix.
For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/ )How to obtain the latest SQL Server 2000 Service Pack
Restart informationYou do not have to restart the computer after you apply this hotfix. However, SQL Server 2000 is automatically restarted when you apply this hotfix.
Registry informationYou do not have to change the registry after you apply this hotfix.
Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article describes. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
SQL Server 2000 32-bit versions
Date Time Version Size File name ----------------------------------------------------------- 06-Jun-2005 22:46 8.11.50523.0 239,104 Mssdi98.dll 12-Jul-2005 17:23 2000.80.2148.0 430,080 Pfclnt80.dll 08-Jul-2005 01:50 2000.80.2148.0 323,584 Sqlagent.exe 08-Jul-2005 02:51 2000.80.2148.0 118,784 Sqldiag.exe 08-Jul-2005 02:09 2000.80.2148.0 102,400 Sqlfth75.dll 08-Jul-2005 16:07 2000.80.2148.0 9,154,560 Sqlservr.exe
SQL Server 2000 64-bit version
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Date Time Version Size File name Platform ---------------------------------------------------------------------- 06-Jun-2005 22:46 8.11.50523.0 758,784 Mssdi98.dll IA-64 08-Jul-2005 16:22 2000.80.2148.0 1,187,840 Pfclnt80.dll IA-64 08-Jul-2005 17:10 2000.80.2148.0 1,061,376 Sqlagent.exe IA-64 08-Jul-2005 16:33 2000.80.2148.0 334,336 Sqldiag.exe IA-64 08-Jul-2005 16:24 2000.80.2148.0 246,784 Sqlfth75.dll IA-64 08-Jul-2005 22:14 2000.80.2148.0 24,935,424 Sqlservr.exe IA-64
To work around this problem, use one of the following methods:
Method 1: Create the RowNumber columnIf the trace table does not contain a RowNumber column, you can add a column that is named RowNumber to the trace table. Or you can re-create the trace table. When you do this, make sure that a RowNumber column exists in the newly created table. For example, if your trace file is named C:\Trc1.trc, use one of the following Transact-SQL statements:
Method 2: Use a version of SQL Profiler that is not updated to SQL Server 2000 SP4The code change that causes this problem to occur is implemented in SQL Server 2000 SP4. Therefore, you can open the trace table by using SQL Profiler from a SQL Server 2000 installation that does not have SQL Server 2000 SP4 installed.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499For more information about the terminology that Microsoft uses when it corrects software after the software is released, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates