Do you have any idea why the ERRORLOG is growing that big?
Are you auditing logins to the ERRORLOG?
There's also a case when you use SqlDependency object for handling query notifications in a .NET app that might cause the ERRORLOG to grow heavily. **[http://support.microsoft.com/kb/958006][1]**
You say that sp\_cycle\_errorlog is not working. Is it giving any error messages, or simply not doing anything?
If you have totally run out of disk space due to the big ERRORLOG file, you might have to delete/move/compress some files to gain enough space to create a new ERRORLOG file.
[1]: http://support.microsoft.com/kb/958006
↧
