August 22, 2003 at 7:57 am
Hi All,
Can you please let me know if Event Log (in Windows 2000/NT 4.0) full situation has any effect on SQL Server Database operations (both online as well as maintenance)?
Thanks in Advance.
.
August 22, 2003 at 10:22 am
No effect. The events are still written to the SQL log. If you have configured events to write to the NT log, they will not be written.
Steve Jones
August 22, 2003 at 11:19 am
Thanks Steve. I am debugging a situation in piece by piece fashion.
.
August 22, 2003 at 3:40 pm
mdamera,
In my experience Windows machines run very oddly when any of the event logs are full. I have had servers that lock up and just in general perform badly when this happens. If your event logs are full I would strongly recommend increasing the size of the log file and enabling the option to overwrite events as needed to ensure new events can be written to them.
Dan B
August 24, 2003 at 6:48 am
Thanks Dan. I would implement.
.
August 24, 2003 at 8:39 am
Also, which event log is full? There are settings to bring down the system if the security log is full. These aren't usually turned on by default, but they can be on servers requiring a high degree of security.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
August 24, 2003 at 8:43 am
Brian,
Application Event Log was full. I have observed that this getting full because of :
"AUDIT-ALL" in SQL Server Properties - Security page. I have just changed it to "AUDIT-Failure".
Also I have C-2 Level Audit turned on. Do I need to turn this off?
.
August 24, 2003 at 8:48 am
C2 Level audit writes into seperate log files in the LOG folder
G.R. Preethiviraj Kulasingham
Chief Technology Officer.
Softlogic Information Systems Limited,
14 De Fonseka Place,
Colombo 05.
Sri Lanka.
Cheers,
Prithiviraj Kulasingham
http://preethiviraj.blogspot.com/
August 24, 2003 at 8:50 am
Preeti,
No It will write into a seperate file in DATA folder. If this file reaches 200MB, it will close this file andd create another file.
.
August 24, 2003 at 9:00 am
No C2 Auditing is through SQL Server. This is different than the Application Event Log. You can alter the Application Event Log size (and Overwrite behavior) by using one of the following:
1) Computer Management
2) Event Viewer
3) Local Security Policy (usually taken care of by your system administrators).
4) Group Policy (if you're under Active Directory and are using Group Policies... but this is probably going to be done by your system administrators).
#2 is the easiest and you can get to it by Start | Programs | Administrative Tools | Event Viewer. Right click on the Application Log and select Properties from the pop-up menu. You'll be able to change the maximum log size and the overwrite behavior from the dialog window that will display.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
August 24, 2003 at 9:03 am
I have changed EventViewer Setting early this morning to be on the safe side.
Thanks Brian.
.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply