Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


SYSDB -> how to reduce its size?

SYSDB -> how to reduce its size?

SYSDB -> how to reduce its size?

I'm writing application with Mimer in Symbian C++. I think that this could be a big problem to deploy database, which at the begining have size ~ 5MB...
Anybody have ay idea?

RE: SYSDB -> how to reduce its size?


Do  you do an export of the database? What kind of compression do you  use? When I have full compression on (remove metadata) my system databanks (sysdb, transdb, logdb, and sqldb) have a total size of 178 KB. When I keep my metadata and remove the systemviews they have total size of 658 KB.

Or do you simply have a lot of data in your databank when you export it to the device?


RE: SYSDB -> how to reduce its size?

Actually yes - I do export of the database and compression works fine. Earlyer i have had a problem with export tool.

RE: SYSDB -> how to reduce its size?

What do you think would be the greatest problem in deploying this database?

Storage space available? Cost of installing Over-The-Air? Application performance?

Personally, if 5 MB is what you get after the database has been compressed, I have only a few ideas about reducing the database further:
- Don't rely on the Mimer database to compress large objects (BLOB:s etc). They are not compressed by the database. For example, if you store pictures, prefer a compressed picture format like JPG, over an uncompressed format like BMP.
- If possible, avoid indexes on large columns. Each index duplicates the data it indexes.
- There are many things to consider but one may be to consider avoiding natural keys. Instead of using the name of a person as key, yuo can use a surrogate, like an integer, which in most cases use less space by foreign keys. Then again, it is possible you have to index the name anyway so you might end up not saving anything.
- Normalize the database. A properly normalized database may reduce its footprint because the normalization reduces duplication of data.

RE: SYSDB -> how to reduce its size?

I think that the greatest problem will be storage space. Before compression whole database had 16 MB - after 5MB. I think that normalization could help. I'll try to do this.
Thanks for help:)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close