Posted by Erland Sommarskog on 10/02/16 11:56

(mollyf@hotmail.com) writes:
> In SQL Server 2000, I could generate scripts in Enterprise Manager and
> then open them up in Textpad or Notepad and make changes if I needed
> to, then go and open the file in Query Analzyer and run it without a
> problem--having to deal with Unicode was never an issue. I should have
> phrased my question better to make it more along the lines of why
> Microsoft changed the default setting, etc. the way that they did.

There is no reason to blame Microsoft for third-party product throwing
away the byte-order mark. Least of all third-party products with only
a half-hearted Unicode support like Textpad.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Problem with export of a table to a text file
• Prev in forum: Re: Setting up scheduled jobs for different days with different intervals
• Thread view: Re: SQL Server 2005 Opening Script File Problem

[Reply to this message]