Re: [sqlite] Vacuum command in a transaction?

On 2013/12/11 01:41, veeresh kumar wrote: Thanks Igor and Simon for your inputs. I was under the impression that VACUUM would also help performance since it does defragmentation. Hi Veeresh, Vacuum does de-fragment the database, it also amalgamates any transaction files and so on - so you

Re: [sqlite] Vacuum command in a transaction?

Thanks Igor and Simon for your inputs. I was under the impression that VACUUM would also help performance since it does defragmentation. On Tuesday, 10 December 2013 3:02 PM, Simon Slavin wrote: On 10 Dec 2013, at 8:04pm, veeresh kumar wrote: >

Re: [sqlite] Vacuum command in a transaction?

On 10 Dec 2013, at 8:04pm, veeresh kumar wrote: > -If we put inside a transaction, definitely we would get a SQLITE_BUSY > error.Any way to avoid this error? It is normal for SQL engines to prevent VACUUM inside a transaction, and to lock the database from other

Re: [sqlite] Vacuum command in a transaction?

On 12/10/2013 3:04 PM, veeresh kumar wrote: I wanted to know what is the good way to execute Vacuum command. - Inside a transaction or without transaction? Doesn't really matter (unless you want to combine it with other statements in a single transaction). VACUUM command is no different

[sqlite] Vacuum command in a transaction?

The database size that we use in the application can grow upto 50 GB. We have an option of shrinking the database using the Vacuum command. I understand that Vacuum command consumes lots of time to execute,but i dont see any other way. I wanted to know what is the good way to execute Vacuum