How to compat native.db

[g_turn0]

I realize that the native.db size is increase gradually, even I deleted some SMS. Now I have ~600 SMS and the phone's perfomance is significant low.
Native.db ~ 1.4MB, but when I delete 200 SMS, its size stay the same!
So, Can anyone know how to "defrag" it or "compact" it to save space and improve phone's speed.
Don't tell me to "master clear". It'll solve the problem but I still want to keep my personal DATA.

[swifty]

in the development-sector is a thread about playing with native.db
maybe there is a solution.
http://www.motorolafans.com/index.ph...ewtopic&t=1074

[g_turn0]

Thansk!
Unfotunately, they just tried to extract information from native.db
Even evaldas tried to restork back to phone, but still no reply for succeed.

has any succeeded dumping native.db and then restoring back to .db file? db_daemon doesn't accept it. tried with db4.1 db4.2 utils

I think if we can extract information and put it back to native.db, we can reduce the size of native.db and make it "solid"

[benjat]

i use to have this probs.. what i do is.. firstly after reflashing my phone and add my personal data, i run the backup script.. and when my native.db is to large, i just delete the native.db, and then run the restore script.. ngee.. i still got my personal data back

[Ator]

I think the database will not get faster if size is smaller. The data is in Memory, so the access time for data should be same, no matter where it is in the file. I don't know BDB enough to tell how space is freed and how indexes are kept in the file.
But I remeber some years ago BDB-files had been significant faster than all othe DB's but could have only ONE index (if I remember right).

One mehod could be to extract the data from the database and save it to a new db in Java (MIDlets also uses BDB's to store data). Maybe it is the same implementation as used internally in the phone. I think I will give it a try. Maybe I write a MIDlet to test it, cause my native.db is also very large after synchonizing 2000 events and deleting them afterwards.