Article ID: 293345
Article Last Modified on 11/6/2003
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition
This article was previously published under Q293345
BUG #: 351185 (SHILOH_bugs)
SYMPTOMS
A SQL script that is saved from SQL Profiler in ANSI file format may not display correctly when opened in Query Analyzer.
RESOLUTION
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 the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
WORKAROUND
To work around this problem either:
- Save the SQL script in UNICODE format from SQL Profiler.
-or-
- Use Notepad to open and save the SQL Script.
STATUS
Microsoft has confirmed that this is a problem in SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.
MORE INFORMATION
Steps to Reproduce Behavior
To reproduce the problem, use these steps:
- Start SQL Profiler.
- From the File menu, point to New, and then click Trace.
- Connect to a SQL Server server.
- Leave the default selections in the Trace Properties dialog box, and then click Run.
- Allow the trace to run long enough to gather several lines of information.
- From the File menu, click Save as..., and then enter SQL Script.
- In the file format drop-down combo box, click ANSI.
- Open the .sql file by using Query Analyzer. Only the first batch captured by the trace displays.
Keywords: kbbug kbfix kbsqlserv2000sp1fix KB293345
