I am considering enabling attachments in several different feature classes. Our Enterprise Geodatabase represents as-built pipeline system features, such as joints of pipe, welds, and valves.
What I would like to do is store pictures on some features and PDFs (such as MTRs) on others. However, I am concerned that the nature of these features will contribute to unnecessary bloat in the size of the database. I will frequently need to store the same single file against multiple different features.
For instance, if I have a valve set of 5 valves all pictured in the same single photo, will using the attachments capabilities result in this single photo being stored 5 times?
Or if I have a batch of 75 joints of pipe, all with the same heat number, and thus all with the same MTR pdf file, will that pdf file be stored 75 times?