Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ErrorLog Size 1

Status
Not open for further replies.

2589

IS-IT--Management
May 5, 2003
8
US
Hi All,

I want to increase the size of the SQL server error log files. I am not able to find where we need to set the value.


Please help me out.

thanks.
 
You dont need to - the error log will keep growing, however a new one is always started each time you restart sql server, or use sp_cycle_errorlog.
 

Thanks for your reply.

But what will be the default size of each file.??

In my instance all the six errorlog files are of 3kb each and when all are filled, the last one is getting deleted and a new file is added and log starts writing to it till it gets 3 KB in size , once it get 3 KB it is again deleting the last one and adding a new one.

so where is the setting for the size of log????

 
Take a look at the logs. At the end of each (latest time) there will be the reason the log was 'stopped'. What is the reason?

Attempting to recycle errrorlog?
SQL Server is terminating due to 'stop' request from Services manager?
Or something else?

-SQLBill
 
Hi,
I checked the errorlogs, and found the follwing messages

"Attempting to recycle errorlog"

" SQL Server is terminating due to 'Stop' request from services manager"

could oyu please elaborate what this messages means??

Thanks
 
Attempting to recycle errorlog

Means you have run the command sp_cycle_errorlog
-----------------------------------------

SQL Server is terminating due to 'Stop' request from services manager

Means the SQL Server Services (MSSQLServer and SQLSERVERAGENT services) have been stopped.
-----------------------------------------
So, the reason your error logs aren't growing larger is that something/someone is stopping them from growing.

Do you have a job that stops the SQL Server services?
Are you or someone else stopping the services?

Since your logs are only growing to 3KB, I would guess that something is stopping your services on a regular basis.

I'm not sure that this will do it, but use Enterprise Manager, drill down to your databases, right click on Master, select Properties, go to the Options tab. Is the database set to AUTO-CLOSE? Check the other databases.

-SQLBill
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top