Is there any downtime or services interruption if changing database from SIMPLE to FULL recovery mode?

Marcus Wong Theen Nam 1,086 Reputation points

I have two databases with around 100GB of size for each db, I am about to change the recovery mode from SIMPLE to FULL for always on availability group setup purposes. As there are users who still using this db, may I know if I just change the mode will it causes any downtime or interruption to the db? How long would it take to complete the changes?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
10,969 questions
SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
433 questions
4,388 questions
0 comments No comments
{count} votes

Accepted answer
  1. AmeliaGu-MSFT 13,931 Reputation points Microsoft Vendor

    Hi MarcusWong-9726,

    Changing database from SIMPLE to FULL recovery model will not cause any downtime or interruption. And it will complete the changes immediately.
    In addition, after switching from SIMPLE to FULL recovery model, please remember to take database full backup to start the log chain and perform transaction log backup regularly. Please refer to this doc for more details.

    Best Regards,

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Navneet Agarwal 1 Reputation point

    No, Changing the recovery mode from SIMPLE to FULL never breaks anything or causes downtime. As mentioned by AmeliaGu, it's recommended to take full backup of database just after changing recovery model from SIMPLE to FULL otherwise consecutive transaction log backup will start failing.

    0 comments No comments