Perhaps. That's what dependency management's for though... Indeed. SQLite is awesome...but the most effective optimisation you can do in software development is do less. Moving the archive data out of the default searches makes finding the stuff you are likely to care about much quicker and more responsive. Less data means better caching. Less work means less instructions, means more spare CPU cycles. More spare CPU means longer battery life. I like having my archive with me...but even I rarely look back. You might do the odd search to find an old message or to see some interesting stats (yay, smscounter)...but even I'll admit that's a poor excuse for slowing down searches for the messages you're receiving now. Nokia recommends archiving your old messages...this is effectively doing that, but making them accessible to well-behaving applications that use the API. Nothing should break...they'll just get a smaller dataset. Perhaps longer than a week...maybe a month or two would be enough...
Yeah...I think it's somewhat ironic that the caching used to make the conversations view work better causes so many problems