Dec 27, 2013 · Shrink can be used to reduce the size of a data or log file, but it is a very intrusive, resource-heavy process that causes massive amounts of logical scan fragmentation in data …

Feb 20, 2017 · If you are concerned about the log size of your MSDB database, try to shrink it once after the first log backup to a size that you expect it to be. A 1GB log size with regular log …

Dec 5, 2012 · Also check why the transaction log file is not releasing the space with the below query- SELECT [name], recovery_model_desc, log_reuse_wait_descFROM sys.databases

Apr 22, 2011 · But there are few log files in different databases of the same server that have the same logical name, can that create problem? Try this little trick - Use the option to shrink the …

Dec 18, 2012 · First of don't shrink your data files, it will cause heavy fragmentation. There are lot of articles out there explaining why shrink is evil. You can Google/Bing for getting them. How …

Apr 24, 2016 · That would be recommended and correct approach. You might need to take backup multiple times and shrink the log. After this is done I suggest you to size your log files …

Aug 12, 2013 · The step failed." I tried to shrink logs after 12:00AM transaction log backup (scheduled for 12:15AM), but did not work. Any transaction log backup occurring immediately …

Mesmo fazendo o shrink da database, e dos arquivos em separado (já tentei todas as opções do shrink) o espaço alocado do arquivo de log continua com 30,9GB. Preciso fazer com que este …

Apr 28, 2015 · By doing this On the instance level go to Security -> Audits -> [Select the audit you want]-> [right click] and select "View Audit Logs" you can see only the current audit log file but …

Jun 29, 2013 · Shrink database/File is not advised unless you are really running out of disk space since it will result more fragementation and shrink will take lots of resources . Do you need to …