I designed a database that stores information about a part, then on a seperate form, allows the user to create a quote of that part.
We now see the need to attach files at the part information level. There will be three separate fields to attach the files.
These files will almost always be PDF's ranging in size of 50kb to 200kb. I'm estimating within a 3-5 year time frame, the file size will breach the 2GB limit.
Is there a way to structure the table/database to reduce the size? I'm thinking about each attachment field have its own table, then that table gets split into its own database. Would this work?
We now see the need to attach files at the part information level. There will be three separate fields to attach the files.
These files will almost always be PDF's ranging in size of 50kb to 200kb. I'm estimating within a 3-5 year time frame, the file size will breach the 2GB limit.
Is there a way to structure the table/database to reduce the size? I'm thinking about each attachment field have its own table, then that table gets split into its own database. Would this work?