I would like to know if there's a way to resize it up to a desired size, or if it is decided by MSSQLS.
In any case, how to do that without compromising the whole database?
I suggest to read this http://technet.microsoft.com/en-us/library/ms189493.aspx
In database file properties you can set the size of the file after shrinking.
I know this is a fairly late post (4 months later), but it jut came up in my feed.
I've just gone through this process for the first time myself and I recommend a good regular maintenance plan.
Backup the transaction logs regularly, and then set the desired size of the log file.
If you are regularly seeing your log file expand beyond what you expect you may need to modify your maintenance plan by taking more frequent transaction log backups or increasing the desired log file size appropriately.
Using DBCC SHRINKFILE is a part of reducing the file size but isn't a cure to the problem of large log files. It will only shrink it by removing free space in the files.
Backing up the transaction log will clear it freeing up space in the existing log file allocated space. This will also stop it growing any larger.
If you set a very small log file you can expect that it will be auto grown by sql server (depending on the settings you configure for autogrowth) every time you shrink it.
It is better to set a realistic log file size initially and manage it.
to restore it fully.
I hope this helps
- Badges
- Science topic