Re: Using findstr on SQL 2005 ERRORLOG file
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 28 Feb 2008 22:33:24 +0000 (UTC)
Teresa Masino (teresa.masino@xxxxxxxxxxxxx) writes:
We have set up a couple of SQL Server 2005 systems and I have found
that the format of the ERRORLOG files and the SQL Agent's log files
are Unicode or some format that findstr cannot parse properly. "find"
parses them fine, but it doesn't have the capabilities that I need --
specifically, I can't search for multiple strings in one search.
I see the checkbox on the SQL Agent's for "Write OEM File", but it is
grayed out so I am not able to try checking that. I also don't know
if that would affect the server's ERRORLOG file too or just the
Agent's log file.
So what am I missing? What is everyone else doing who is used to
having scripts to parse these files looking for strings that indicate
problems? Is there a server setting that will force it to go back to
a plain ANSI text file format for log files? Is that a bad thing to
do?
I doubt there is a setting to force the SQL Server error log to be ANSI.
Would be a lot problem to log object and database names with characters
outside the ANSI set in that case.
I guess the answer is to use Unicode-capable tools. I don't have any
real suggestion for that. I search the errorlog fairly rarely, so most
of the time I'm content of opening it in Textpad. (Which understands
Unicode in so far it can handle the encoding, but it's not able to
work with characters outside the ANSI range.)
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
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
.
- References:
- Using findstr on SQL 2005 ERRORLOG file
- From: Teresa Masino
- Using findstr on SQL 2005 ERRORLOG file
- Prev by Date: Re: Why Same query results in two different # in SQL Server vs MS Access
- Next by Date: Re: Transfering data from SQL Server Standard to SQL Server Express
- Previous by thread: Using findstr on SQL 2005 ERRORLOG file
- Index(es):
Relevant Pages
|
