Bobcares

Auto shrink database property in SQL server – Why should we turn it off

by | Jan 28, 2021

Auto shrink database property in SQL server allows to automatically shrink the database files if the value is set to ON/True.

However, it is not a good practice to shrink a database. Because it is a very expensive operation in terms of I/O, CPU usage, locking, and transaction log generation.

It is only recommended to shrink the database in cases like data deletion. That is we can run the shrink operation if we’ve deleted some portion of the data to retrieve that space back. Also, we need to ensure that we rebuild the fragmented indexes post performing the shrink operation because this can cause index fragmentation.

Here at Bobcares, we receive requests from customers relating to AutoShrink property in SQL as part of our Server Management Services.

 

Why we must not enable Auto shrink database property in SQL server

Here are the different reasons why the auto shrink property must not be enabled for the database.

  • It will cause index fragmentation which in return reduces the database performance.
  • Shrink operation takes a lot of IO and CPU resources. As a result, it may cause long disk queue lengths and possibly IO timeouts.
  • Repeatedly shrinking and growing the data files will cause file-system level fragmentation. As a result, it will slow down performance.
  • Growing the database in small increments or growing it and then shrinking can cause disk fragmentation. This can cause performance issues.
  • It slows down the database server. Because shrinking is a heavy load operation that would take a long time to complete.
  • It is unpredictable. Because the Autoshrink operation can start at any time, maybe during the peak time.

 

How to enable or disable the AutoShrink operation in SQL Server.

Now let’s take a look at how our Support Engineers enable and disable the AutoShrink database property.

  1. We can turn it On or Off using the SQL Server Management Studio or T-SQL code.
  2. First, we right-click on the database for which we need to enable or disable the AutoShrink. Then we choose the Properties.
  3. Next, on the Database Properties window, we click on the Options from the left side pane.
  4. Now, we can see the AutoShrink option on the right side of the pane. If we wish to turn it On/Off we can click on the drop-down of the option and select True/False.
    auto shrink sql server

Here is the T-SQL code to enable or disable the AutoShrink option for any database.

Set Auto Shrink ON or True

ALTER DATABASE DBName SET AUTO_SHRINK ON

Set Auto Shrink OFF or False

ALTER DATABASE DBName SET AUTO_SHRINK OFF

[Need any assistance with SQL queries? – We’ll help you]

 

Conclusion

In short, it is not recommended to enable the AutoShrink database property as it can cause many issues in the SQL Server. Today, we discussed what happens if enable this property. Also, we saw how our Support Engineers enable and disable this database property.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

2 Comments

  1. Kadee74

    It depends on the context, imo. On a TEST server with many databases and many developers running/trying scripts that sometimes result in an explosion of the tranaction LOG, it can have benefit from auto shrink?

    Reply
    • Hiba Razak

      Hi,
      it is not recommended to use auto-shrink as a long-term solution for managing the transaction log size, as it can cause more problems than it solves.Instead, it is better to properly manage the transaction log size by regularly backing up the transaction log and ensuring that the log is truncated after each backup.

      Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF