What are the Database Limits

The_Anomaly

I searched the forum but didn't see something like this, maybe I missed it though.

Background: I have worked on AwareIM on a very big project and know how rapidly one can design.

Problem: I have a new client who has a project 3 years running now. This website is core to their business. There is one problem though before purchasing:

Does AwareIM store pictures in the database? Their business is asset tracking and auditing of sorts. Which means they take lots of photos of items in place at there destinations as proof of delivery. Currently the website is in PHP and the core is small BUT the images are stored on disk and the site now sits at 9GB!!

Not any database would be suitable for this! Can AwareIM handle 9GB, and growing, of binary data in its DB - seems MySQL can't and I'm not a fan of Derby as there aren't any tools for designing triggers, views etc.

Any advice?

pbrad

Hi,

You might want to consider storing the images outside of the database in a file system and keeping the path reference to the images in the database only. There are several threads in this forum that explain how to do this.

Cheers,
Pete

aware_support

If you want to store images in the database, consider using SQL Server - it will probably handle such storage requirements...

kklosson

Interesting discussion. I am planning on using MySQL. My system will store some images and some files, though just a few related to each record and this is not the main thrust of the application. I have no idea how MySQL is storing them.

But considering this, should I consider deploying with MS SQL vs MySQL?

RocketRod

I go along with Pete. Yes store small amounts of pictures and files within the DB itself but for large volume I would always store on disk and just hold the links within AwareIM. I operate large SQL databases running an ERP and would not recommend storing the pictures within the DB. By placing them on disk you give yourself:

Flexibility as you never know you may want to move them to another storage area one day.
Less headaches with backing up and restoring the SQL DB.
Peace of mind as you can SEE the picture files and play with them outside of the DB and they are not hidden away in a picture attribute of a BO.

Cheers Rod