SolarWinds dbo.SysLog is too big

Our SolarWInds web console stopped responding for what I presume is the syslogs being too big.  I see the following error in the logs:

2014-10-22 15:02:57.33 spid62      Error: 1105, Severity: 17, State: 2.
2014-10-22 15:02:57.33 spid62      Could not allocate space for object 'dbo.SysLog'.'IX_SysLog_DateTime' in database 'SolarWindsOrion' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

I am not a SQL kind of guy and would to know of there is any statements I can run to trim this thing.  I am not interested in saving data older than 60 days.  Also, where in the console can I change these settings so the database doesn't get this big.

Thank you!
IDMAAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
For now I think the best thing to do is to provide some extra space for the file can grow.
I don't know SolarWinds but if we are talking about logs, shouldn't be a way to configure how old data should be purged?
By the error message I can guess a DELETE command to run in SQL Server:
DELETE FROM _Syslog WHERE DateTime < GETDATE()-60' 

Open in new window

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jogosCommented:
"the syslogs being too big"
That is al relative, but surely now it needs more space.    Before deleting in the heat of the batle look at some things.
- is table/index realy big, more than you expect .... and how long is that data going back (so you know the limit)
- why can database not grow, lack of disk or not configered to grow
- when deleting know that your transactionlog will grow that can hit limits too (and if disk is the problem .... ) and it could help if you know if your db is in full or simple recovery mode.
0
eeRootCommented:
The Solarwinds Syslog server can be set to discard unneeded or informational messages.  If you view the syslog entries, are there a large number of any unneeded messages?  Often, the port up/ port down messages need to be deleted to prevent the syslog db from getting too big.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.