PErformance and SQL Server Error Log

I am using SQL 2K.
Size of the SQL Server error log file will degrade the performance of SQL
Server.
I am talking about log file which I cleared using SP_CYCLE_ERRORLOG.
Thanks,
JJRecycle more often then. How did you determine that it "degraded"
performance?
bert|||Sorry,
It was my quetion as whether it will degrade the performance or not?
Thanks,
JJ
"bert" <bertcord@.gmail.com> wrote in message
news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> Recycle more often then. How did you determine that it "degraded"
> performance?
> bert
>|||Hi
Not that I have ever found. Output to the log file is appended and is not
read by SQL Server itself.
The bigger issue is how do you view it. A 10Mb log file does take a while to
open in EM (or notepad).
We cycle our error logs on our 400 servers every night. This helps us to
keep the Error log entries by day.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"John Smith" <JJSmith45@.hotmail.com> wrote in message
news:#bkfy5KCFHA.3524@.TK2MSFTNGP15.phx.gbl...
> Sorry,
> It was my quetion as whether it will degrade the performance or not?
> Thanks,
> JJ
> "bert" <bertcord@.gmail.com> wrote in message
> news:1107297013.482698.267950@.l41g2000cwc.googlegroups.com...
> > Recycle more often then. How did you determine that it "degraded"
> > performance?
> >
> > bert
> >
>|||"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.|||Another helpful hint: either by registry key or by using SQLEM, you can
modify the properties of the SQL Error logs to increase the number retained.
We set ours to 32 and recycle at 11:59 PM every night.
Another thing to consider, most of what is output to the SQL Server Error
logs also ends up in the server's Application Event log; so, you might want
to increase the size of that log too.
Finally, if you have your security settings to Audit all logins, both the
SQL Server Error logs and the system's Application Event logs can be
enourmous. We currently only set for failed login attempts.
Sincerely,
Anthony Thomas
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:EthMd.26166$ZD1.5393@.twister.nyroc.rr.com...
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:euXu08KCFHA.1936@.TK2MSFTNGP14.phx.gbl...
> Hi
> Not that I have ever found. Output to the log file is appended and is not
> read by SQL Server itself.
> The bigger issue is how do you view it. A 10Mb log file does take a while
to
> open in EM (or notepad).
> We cycle our error logs on our 400 servers every night. This helps us to
> keep the Error log entries by day.
>
We do it on the first of the month. But same idea.. keep it somewhat
reasonable and have enough "old" ones to troubleshoot problems.