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

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Information about whether you must restart the computer after you install the hotfix package
• Information about whether the hotfix package is replaced by any other hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

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.

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:

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:

• You create a trace file by using SQL Profiler.
• You import the contents of the trace file to a table by using the fn_trace_gettable function

Therefore, when you try to open this trace table by using SQL Profiler, you receive the error message that is mentioned in the "Symptoms" section.

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

• The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.
  
  Note This issue does not occur on systems that use the Intel Itanium processor architecture.
• The system is running a 64-bit version of the Microsoft Windows Server operating system.
• The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information

A 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: Note 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.

Prerequisites

You 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:

Restart information

You 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 information

You do not have to change the registry after you apply this hotfix.

Hotfix file information

This 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

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.

To work around this problem, use one of the following methods:

Method 1: Create the RowNumber column

If 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:

• SELECT *, Null as RowNumber INTO temp_trc FROM ::fn_trace_gettable('c:\trc1.trc', default)

• SELECT IDENTITY(int, 1, 1) AS RowNumber, * INTO temp_trc FROM ::fn_trace_gettable('c:\trc1.trc', default)
  

Method 2: Use a version of SQL Profiler that is not updated to SQL Server 2000 SP4

The 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: For 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: