March 8, 2013 at 2:51 am
Hi,
In my C: drive where my sql runs i have only 2 GB left.. I checked log spaces for all databases i found that my one of my production db is 123 GB in size and having a log space of 19 GB. Can i shrink that log file .
March 8, 2013 at 2:55 am
First why is the log on the C drive and not on a different drive?
What is the activity of the databases? Is it likely that the file will get to 19GB again? Do you do transaction log management? What is the log_wait_reuse_desc column from sys,databases saying? What is the recovery model of the DB?
March 8, 2013 at 3:39 am
Hi
Recovery model is full
log_reuse_wait_desc says Log_Backup
there are only two drives in system as i can see only two from XP_fixeddrives.
both mdf and ldf 's going to E drive.
Transactional Backup plans are there and running fine now... but from job history i can see that the job failed for last 6 days.
the database is connected to OLTP application.
March 8, 2013 at 3:48 am
Well if your LDF is on the E drive shrinking it isnt going to help your C drive.
Would seem to me like you need to get some monitoring on your jobs, 6 days of no transaction log backups I would be out of a job and looking for any other one.
Edit
I would seriously look at your sever specs as well, 1 drive for both your MDF and LDFs, also are your backups going to the same drive?
Get separate disks on separate RAID arrays, 1 for data 1 for logs 1 for backups to protect yourself, and if you can RAID 10.
March 8, 2013 at 5:51 am
anthony.green (3/8/2013)
I would seriously look at your sever specs as well, 1 drive for both your MDF and LDFs, also are your backups going to the same drive?Get separate disks on separate RAID arrays, 1 for data 1 for logs 1 for backups to protect yourself, and if you can RAID 10.
Seriously, I hope you take Anthony's comment to heart. You should have a system drive, a data file (MDFs) drive, a log file (LDFs) drive and a backup drive. Obviously, this is for performance, but also for disaster planning. If disaster strikes the single drive and you have everything on there, you're dead in the water.
The backups should end up on a different machine eventually. Part of disaster planning includes thinking about disasters - not only with the machine, but also the environment. If you had a fire in the building, would your data be safe? Is it sent off somewhere safe? This type of thing is all overhead and not usually taken seriously until it's needed. The trick is to plan before you need it.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply