About a month or so ago I inherited this somewhat-new database. I was lead to believe that everything was set up and all maintenance tasks were running without a hitch. SQL Server 2008 R2
I was looking at it today while trying to troubleshoot some slowness and discovered that we are almost out of space on our ~500gb array. We have multiple tables whose sizes are upwards of 6gb, which I'm not too concerned about. BUT they have corresponding log files that are around 5x the size! One of them is 31gb. Their modification dates are 3 days ago. The little I have read leads me to believe this is incorrect.
- Can I safely truncate these log files?
- How often should I do this, and when? (The nightly backup is at 12am.)
- I see no re-indexing, statistic updating, etc. Is it safe to go ahead and set these tasks up? Should I wait until after the aformentioned truncation?
- Can the software writing/reading to the database be used while these tasks are being performed? We are 24 hours and stopping production is very difficult.
- We also have a LOT of backup files. Like, one for every table for every day since February. Can I delete some of them? Is there a way to set the backup to do this automatically?
Thanks so much guys. We have an IT department but I'd rather not have to wait on them, especially if these things are easy to do. I'd rather set them up myself (if possible) and let a DBA check in on them occasionally.