FIX: ANSI Script from Profiler Cannot be Opened in Query Analyzer

This article was previously published under Q293345
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 351185 (SHILOH_bugs)
A SQL script that is saved from SQL Profiler in ANSI file format may not display correctly when opened in Query Analyzer.
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
To work around this problem either:
  • Save the SQL script in UNICODE format from SQL Profiler.

  • Use Notepad to open and save the SQL Script.
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.

Steps to Reproduce Behavior

To reproduce the problem, use these steps:
  1. Start SQL Profiler.
  2. From the File menu, point to New, and then click Trace.
  3. Connect to a SQL Server server.
  4. Leave the default selections in the Trace Properties dialog box, and then click Run.
  5. Allow the trace to run long enough to gather several lines of information.
  6. From the File menu, click Save as..., and then enter SQL Script.
  7. In the file format drop-down combo box, click ANSI.
  8. Open the .sql file by using Query Analyzer. Only the first batch captured by the trace displays.

Article ID: 293345 - Last Review: 01/16/2015 22:03:55 - Revision: 3.2

Microsoft SQL Server 2000 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbsqlserv2000sp1fix KB293345