Simply shrink transaction log file (ldf file) as youe have done with mdf file.
Is the .ldf file just events from ePO? If so would it be possible to create a new .ldf file?...detach current DB -> rename or move .ldf file -> attach DB that was just detached ?
I've tried. Gone to shrink -> files and databases, reduces the size by a few hundred Meg which isn't enough. I don't think I can select only the ldf file to shrink.
No - the .ldf file is the SQL transaction log for the database, and as such is an integral part of it. Which version of SQL are you using, and what recovery model have you set for the ePO DB?
I'm using SQL server 2005 express (SQL Server 9.0.5000). Recovery Model is full, could that be the cause?
After shrinking the DB yesterday the size of the .ldf file was about 16G, I just checked this morning and its at almost 19G now.
Recovery Model is full, could that be the cause?
If the recovery model is Full or Bulk-Logged, it means that the transaction log will just keep growing: you are responsible for maintaining it. This is one of the reasons that we recommend using the Simple model - it means that SQL manages the transaction log for you.
Stop the ePO services, change the recovery model to Simple, and shrink the database again - the transaction log should almost vanish
I think if you do a full backup (SQL Server's backup tool, not just copy the files somewhere), then shrink the log file, it will get much smaller. Also, if you switch to the simple recovery model, the log file won't get so big. I don't remember exactly what the difference between the recovery models is, but you should be able to find info on it in the SQL Server help and determine which model is best for you. Also check how the log file is set to grow. If it is set to grow by percentage, the larger it gets the more it will grow each time it fills up.
Thank you Joe! Issue resolved. Transaction log is down to 504KB now.