Hey,
Have a little predicament, I have created a database which works great, But after a little under a month of use its now at 1.7 GB
We store a lot of images in our database because it logs build issues and people attach images of problems / solutions / drawings to records.
There are 10 tables in total, 3 of which will be attachment heavy.
I was thinking do I split it into multiple backends, or is there another way? I am aware that if I do split into multiple backends then I will need to code the RI, and I have no clue how to do this.
I also can't move it to SQL due to company rules.
Thanks for any advice you may have.
Cat
Have a little predicament, I have created a database which works great, But after a little under a month of use its now at 1.7 GB

We store a lot of images in our database because it logs build issues and people attach images of problems / solutions / drawings to records.
There are 10 tables in total, 3 of which will be attachment heavy.
I was thinking do I split it into multiple backends, or is there another way? I am aware that if I do split into multiple backends then I will need to code the RI, and I have no clue how to do this.
I also can't move it to SQL due to company rules.
Thanks for any advice you may have.
Cat