I'm trying to make an argument against my client's desire to embed documents into a database as opposed to having links to files/document/spreadsheets/images, etc. in a related table - which is how I designed it. They had an IT person on staff who thinks embedding these files makes more sense.
I explained bloating, unnecessary network traffic, files becoming static instead of dynamic (they said they'll delete the files once embedded), etc.
Right now the back-end is an Access db -- but migrating to another back-end is not out of the question.
I have never even considered embedding files into a database as I was trained that it's not a good idea. Can you provide me some solid arguments or recommend a db that would handle this??