Will you be putting more IIS log records into the database? If yes, they will simply take up the db available space previously occupied by the deleted records the database size will NOT increase until all the available 'deleted' space has been re-used. You say you are storing logs for IIS in this database, and you have deleted some old records.
#What files can be deleted with sql 2012 express full#
If in Full without proper full and differentials. I dont advise this though without further investigating the backups and recovery model of this particular DB. If you truly want to shrink this file ( pointless if you are still logging the same levels at the same frequency in whatever app puts the iis info in there its just going to grow again to accommodate the records) you can right click the db and hit the tasks submenu and go to the shrink section. If you have purged the records out the worst case is a data file that has more room in it and a tlog that needs a backup to clear out the transactions. I'd first be more concerned about making sure the backups are in place before adjusting the size of anything. If you perform an ad hoc backup without specifying copy_only you will break the log chain. ****That said be careful, Full recovery requires a full and t log backups. if at all), but this means you can do a "point-in-time" recovery in the event of a failure: you can restore the latest full backup, then use the transaction log backups to recover to just before the issue started. This tends to make the log larger (depending on how often you run the log backups.
When a transaction completes, it will stay in the transaction log (ldf) until you perform a transaction log backup.
See img attached.ĭepending on recovery modes as well you will see the ldf continue to grow without a proper backup job in place. Do you know if the 63.7gb ldf is full? You should be able to right click the DB and see that in the properties. File sizes mean less than how empty the files are.
0 kommentar(er)
