Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We had a user change a password on an account that was on an automation equipment that pinged the sql server many times a second (for no apparent reason - the pinging).

In the end my errorlog ballooned out to >6gb, and my hard drive isn't large enough to accomodate that.

I've cycled it, but it's still at the 6gb.

Is there a way to reduce that?

Thanks

share|improve this question
up vote 5 down vote accepted

I am not sure of the exact number, but SQL Server will hang on to the previous 6 errorlog files.

Try the following at least 7 times:

EXEC sp_cycle_errorlog;
GO

Source: sp_cycle_errorlog (Transact-SQL)

share|improve this answer
1  
We were cycling the sqlagent error log but needed to cycle this one also. – crucible Sep 18 '12 at 5:38

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.