DB Options:- Auto Shrink =OFF and why shrinking is bad скачать в хорошем качестве

DB Options:- Auto Shrink =OFF and why shrinking is bad

The use of AUTO SHRINK I think needs no explanation. Almost anybody who has worked on SQL Server understands the way databases can quickly grow. In these cases we can see growth happens in two places, the database file and the log file. The database file gets highly fragmented when it is shrunk. The log file being sequential doesn’t suffer from this issue. Therefore it is ok to shrink the log file when needed but data files should not be shrink unless you’re trying to recover space as a last resort or empty a file. Having understood what should and should not be shrunk we next explore if this should be setup as a database option. The quick answer is NO. We have no control over when the automatic shrink will occur and because shrinking causes massive amounts of IO, we encounter performance issues. Shrinking can also run for long duration and cause locks making things worse. Shrinking the database is something we should have full control over since it causes performances issues. Need more information? Visit https://www.enabledbusinesssolutions.com To know more about Jayanth Kurup visit http://www.jayanthkurup.com Jayanth is a Microsoft SQL Server trainer / consultant with over 15 years’ experience. He has worked with companies like Microsoft, IBM, HCL, Wipro, Well Fargo, Zeomega and many more. He is based out of Bangalore and a very active member of the SQL Server Community. In this channel he covers complex topics related MS SQL Server , PowerBI , Azure , AWS , Powershell, SSIS , SSAS , SSRS , Machine Learning , AI , etc You can also reach Jayanth via his LinkedIn profile below www.linkedin.com/in/jayanth-kurup music from HAAWK