April 7, 2008 at 9:28 am
All of the ErrorLog files on our SQL Server 2005 instances are unicode files. I was looking for a way to convert the unicode Errorlog file to an ASCII file. I found information online indicating that the option Write OEM file in the General properties of the SQL Server Agent will do this, yet when I go to that screen the option is grayed out.
Does anyone know if there is some way to enable this setting? We only deal with ASCII character sets so there is no need for any unicode files at our company.
We are running SQL Server 2005 Standard SP2. No cumulative update packages have been applied. I looked through the fix lists for the cumulative update packages but I did not see any information regarding this setting.
Thank you in advance
- John
April 23, 2008 at 10:30 am
The TYPE command will convert unicode to ASCII. i.e (from a batch job).
TYPE \\SQLSRVR1\E$\MSSQL.1\MSSQL\LOG\ERRORLOG > \\SQLSRVR1\C$\ERRORLOG\ErrorLog.txt
Dan
April 23, 2008 at 10:45 am
Cool. Do not copy to the original log name.
What are you doing with the log?
Regards,Yelena Varsha
April 23, 2008 at 11:53 am
Over 60 SQL server error logs are read by a VB script every 30 minutes which notifies SQL DBAs of any errors found.
Dan
April 23, 2008 at 11:59 am
That's great dlcook, thanks!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply