![]() ![]() While shrinking the database, you must have to consider shrinking operations on both critical as well as relatively larger databases as a part of maintenance. Moreover, you must need not worry about the size fragmentation of database files. In the scenario where you have a number of relatively small databases that grow to a larger size either by insertion of new tuples or by a large number of empty spaces created by deletion of several tuples, SQL Server Auto Shrink becomes pretty handy in this situation. ![]() SQL Server Auto Shrink feature is disabled by default on SQL Server instance databases. Database Administrator must schedule a transaction log backup to reduce the size of log files at a fair size. If you back up the database, it releases the free space to be reused again. Transaction logs will increase in numbers until it occupies all the available disk space if you don’t take back up of them. Backing up the whole database is not a good idea one must construct or set up the transaction log also. To avoid the activity of shrinking of data/log files whenever file size surpasses the free space in the data file, DBA (Database Administrator) must back up the log files at a regular interval. Automatic shrink operation is done by the server auto shrink database feature, which is the main course of this article. In this article, we will discuss the SQL Server Auto Shrink database property, which allows SQL Server to automatically shrink the database files when the value is configured as True in the database option. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |