the Server crashes down.
How can I make that the [Error_Log] goes not over 20MB '
Have I got to (re)start the Instance every day ' Or is
there another good way to keep the Server alive.
Thanks. RogerThis is a multi-part message in MIME format.
--=_NextPart_000_000E_01C396DC.2B8BCE60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To have an error log go that high is extremely unusual. To have a =database transaction log go that high is not so unusual. Are you sure =it is the error log?
-- Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
.
"Roger Bossard" <rbossard@.dfs.ch> wrote in message =news:08ad01c396fc$ac7cf060$a101280a@.phx.gbl...
The SQL_Server Error_Log begins to raise up to 72 GB, then the Server crashes down.
How can I make that the [Error_Log] goes not over 20MB ' Have I got to (re)start the Instance every day ' Or is there another good way to keep the Server alive.
Thanks. Roger
--=_NextPart_000_000E_01C396DC.2B8BCE60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
To have an error log go that =high is extremely unusual. To have a database transaction log go =that high is not so unusual. Are you sure it is the error =log?
-- Tom
----Thomas A. =Moreau, BSc, PhD, MCSE, MCDBASQL Server MVPColumnist, SQL Server ProfessionalToronto, ON Canadahttp://www.pinnaclepublishing.com/sql">www.pinnaclepublishing.com=/sql.
"Roger Bossard"
--=_NextPart_000_000E_01C396DC.2B8BCE60--|||To add to Tom's comments and in case it is the errorlog, you can schedule a
job to check the size of the errorlog regularly. If the size crosses a
threshold, run sp_cycle_error (or dbcc errorlog) to start a new errorlog.
This doesn't require the SQL instance to restart.
If it's a transaction log, you should run BACKUP LOG regularly to contain
its size. By the way, why do you want to restrict its size to 20MB (if it's
a tran log file)?
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:egUi62vlDHA.2416@.TK2MSFTNGP10.phx.gbl...
To have an error log go that high is extremely unusual. To have a database
transaction log go that high is not so unusual. Are you sure it is the
error log?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
.
"Roger Bossard" <rbossard@.dfs.ch> wrote in message
news:08ad01c396fc$ac7cf060$a101280a@.phx.gbl...
The SQL_Server Error_Log begins to raise up to 72 GB, then
the Server crashes down.
How can I make that the [Error_Log] goes not over 20MB '
Have I got to (re)start the Instance every day ' Or is
there another good way to keep the Server alive.
Thanks. Roger
No comments:
Post a Comment