{"id":3193,"date":"2015-12-01T09:32:36","date_gmt":"2015-12-01T14:32:36","guid":{"rendered":"https:\/\/academy.sqlbak.com\/?p=3193"},"modified":"2023-10-17T05:25:51","modified_gmt":"2023-10-17T09:25:51","slug":"full-recovery-model","status":"publish","type":"post","link":"https:\/\/academy.sqlbak.com\/full-recovery-model\/","title":{"rendered":"Full Recovery Model"},"content":{"rendered":"

In the full recovery model SQL Server does not truncate committed transactions until they have been backed up. It allows the creation of full, differential, and transaction log backups thus making point-in-time recovery possible.<\/p>\n

You need to keep in mind that in the full recovery model, the transaction log file would be much larger, and you have to make regular log backups to keep it small.<\/p>\n

Here are some tips on when the full recovery model is better to use:<\/p>\n