Nightly process to either :

-- Compress and/or reduce the dpi of documents found in
the DOC table.

-- DOC table link-able to another storage platform for cross-year storage to eliminate duplication during roll-over ( examples: Another external DB, Google Team Drive, Amazon Glacier, Share Point ).

Goals:
-- Reduce the size of the Aeries Annual DBs
-- Improve daily performance
-- Allow for better backup & retention policies.

Background: In school year 2018-2019 we started using the DOC table to go 'paperless'. While this is a good
feature for our staff, it caused our DB size to balloon well over 10+ GB. Over the course of a 12 year academic
record, we anticipate our current-year Database will grow 100+ GB and have roughly the same amount for
each prior year ( since the documents will duplicate for the rolling over students ).
Ideally if we could have Aeries reduce the size of the binaries stored ( nightly process, during upload, or
manual back-end function ) it would be greatly appreciated. Aeries already does a similar process for the Pic
table ( it keeps a different size image for each student picture upload ).
Also if the DOC table was stored in an external Database or System ( examples: Another external DB, Google
Team Drive, Amazon Glacier, Share Point ), we could eliminate the duplication from year-to-year roll-over.
Also allows each district to set different backup & retention policies for DOCs and for the rest of Aeries.