We have a SQL Server-based SDE database powering an offline service for one of our apps (Archiving & Attachments). The database is currently about 800MB with all the photo attachments. We just moved this data into the database so we know we don't have large archive tables messing with things.
When we try to trigger a new database download the server generates a .geodatabase file of over 2.4GB, before the process fails.
Why is this database so much larger than the parent SQL Server database? If we extract all the attachments as images in a directory they add up to right around 800MB so I'm at a loss where all this additional data is coming from.