I am managing a number of SQL Server instances and realize
that a new SQL Server Error Log (MSSQL\LOG\ERRORLOG...)is
created each time the instance is started. At this
location we do not "bounce" the SQL Servers on any kind of
a schedule and the Logs do not cycle more than maybe once
every couple of months. One in particular has not swithed
since early September.

Is it necessary to switch them periodically?

Should I use the package sp_cycle_errorlog and schedule
switching of the SQL Server Error Logs?

Report this post to a moderator

There are no technical issues that I know of if you don't swap them on a
regular basis. But they can be easier to manage if they are cycled every so
often to keep their size down.

--
Andrew J. Kelly
SQL Server MVP


"Otto Naesset" <ojn@itpnet.com> wrote in message
news:1838101c29578$b6517100$89
f82ecf@TK2MSFTNGXA01...
> I am managing a number of SQL Server instances and realize
> that a new SQL Server Error Log (MSSQL\LOG\ERRORLOG...)is
> created each time the instance is started. At this
> location we do not "bounce" the SQL Servers on any kind of
> a schedule and the Logs do not cycle more than maybe once
> every couple of months. One in particular has not swithed
> since early September.
>
> Is it necessary to switch them periodically?
>
> Should I use the package sp_cycle_errorlog and schedule
> switching of the SQL Server Error Logs?
>

Report this post to a moderator

I cycle the logs using sp_cycle_errorlog on a scheduled basis. I've found
that's its easier/less error prone to review smaller logs and that large
logs will take longer to open.

"Otto Naesset" <ojn@itpnet.com> wrote in message
news:1838101c29578$b6517100$89
f82ecf@TK2MSFTNGXA01...
> I am managing a number of SQL Server instances and realize
> that a new SQL Server Error Log (MSSQL\LOG\ERRORLOG...)is
> created each time the instance is started. At this
> location we do not "bounce" the SQL Servers on any kind of
> a schedule and the Logs do not cycle more than maybe once
> every couple of months. One in particular has not swithed
> since early September.
>
> Is it necessary to switch them periodically?
>
> Should I use the package sp_cycle_errorlog and schedule
> switching of the SQL Server Error Logs?
>

Report this post to a moderator

Limiting the size on servers with high uptime improves
the ability to review the logs from within EM. If you wish
to keep more logs to compensate for their smaller size then
you can use EM to configure the number of logs to keep.
i.e. you might want to keep 10 instead of the default 6.
To do this right click on SQL Server Logs in EM left pane
and choose Configure from the menu. Tick the checkbox
and enter 10 in the spinbox.

--
HTH

Jasper Smith (SQL Server MVP)

"Otto Naesset" <ojn@itpnet.com> wrote in message
news:1838101c29578$b6517100$89
f82ecf@TK2MSFTNGXA01...
> I am managing a number of SQL Server instances and realize
> that a new SQL Server Error Log (MSSQL\LOG\ERRORLOG...)is
> created each time the instance is started. At this
> location we do not "bounce" the SQL Servers on any kind of
> a schedule and the Logs do not cycle more than maybe once
> every couple of months. One in particular has not swithed
> since early September.
>
> Is it necessary to switch them periodically?
>
> Should I use the package sp_cycle_errorlog and schedule
> switching of the SQL Server Error Logs?
>

Report this post to a moderator