I am confused about the maximum limit of the SQL database if there is one. Soon, I’m going to upload images to SQL, and they could vary from 200-400KB for each image; the total database can reach up to 100MB to 1GB* in the future. So, if Infinity-Free SQL has any limit, please let me know. I could not find any reliable source to verify the maximum limit.
Why are you storing images in database?
My guess is that he wants to bypass the inode limit in a way to save files in a blob (DB)
Currently, I’m not directly storing images in the database I am using image links, but I want to give users an option to directly upload images instead of links.
Yes one of my reasons, the inode limit is also a big problem
Storing the images in an external service and having links to them in your database can also work as a solution if it turns out you can’t use the database to directly store images in it.
I am already doing that, I just want to give users an option so they can upload an image directly instead of creating a link because some users just want to use the image upload button instead of creating an image link. so I am creating a second option for those users.
But how is storing images directly to the database going to solve that?
I’m sorry, what do you mean by solving what?
Using a MySQL database for bulk file storage is definitely not how they are intended to be used. There are no hard limits on it, but if we see that the storage of the database server is getting full and 90% of the usage is caused by your site trying to circumvent the storage limit on your hosting account, we will take action, and it won’t be pleasant for you.
If you’re looking for scalable storage for images, I would recommend to use object storage, like Amazon S3, instead. People can then upload images to your site, which your site then uploads to this external storage service, where you can link to the images. Services like that charge you for the disk space you use, and typically only costs a few cents per GB, without limits. Then, in the database you only need to store a reference (URL) to the file on object storage so you can show the right URL to your visitors.
I hope this is what you asking for, This is how it helps, previously if directly uploading an image link after manually compressing an image using Tinify, but it time-consuming, with tinity API it only gives a 500 image compression limit but compression is worse 1.3MB can only be 600kb - 800kb*.
Currently, I’m using PHP inbuild > “extension=gd” for image compression, then the compressed file will convert to > binary string, and in PHP I use “base64_encode” in PHP to convert back to image format, this way the image size becomes 1.3MB to just 50-150KB*, but I still dont know what is limit of Infinityfree, so I am a little bit scared
Thank you for letting me know, where can I see how much storage of the database server % I have been using yet?
Thank you, I will definitely consider it.
We don’t provide this information. We don’t show database size, and there is no need for you to know the total amount of disk space of the database server either. The 90% mark isn’t a hard limit though, but there is monitoring that notifies server admins if storage is running low. And if they find out that one account is responsible, they will take action.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.