COMPRESS SQLITE DATABASE HOW TO

If you shrink a database repeatedly and notice that the database size grows again, this indicates that the space that was shrunk is required for regular operations. Most databases require some free space to be available for regular day-to-day operations. For more information, see Display Data and Log Space Information for a DatabaseД¬onsider the following information when you plan to shrink a database:ДЄ shrink operation is most effective after an operation that creates lots of unused space, such as a truncate table or a drop table operation.

To view the current amount of free (unallocated) space in the database.

Conversely, you cannot backup a database while a shrink operation on the database is in process. You cannot shrink a database while the database is being backed up. For example, if a database was originally created with a size of 10 MB and grew to 100 MB, the smallest size the database could be reduced to is 10 MB, even if all the data in the database has been deleted. The minimum size is the size specified when the database was originally created, or the last explicit size set by using a file-size-changing operation, such as DBCC SHRINKFILE. The database cannot be made smaller than the minimum size of the database.

When enough free space is created at the end of the file, data pages at end of the file can be deallocated and returned to the file system. Shrinking data files recovers space by moving pages of data from the end of the file to unoccupied space closer to the front of the file.

COMPRESS SQLITE DATABASE HOW TO

This article describes how to shrink a database in SQL Server by using Object Explorer in SQL Server Management Studio or Transact-SQL. Applies to: SQL Server (all supported versions) Azure SQL Database

Compress sqlite database