Store ServiceNow attachments on 3rd Party System without losing it's relationship

[Lucas Sim_es1]

Hello Experts!

We're facing an issue at my company where the sys_attachment_doc table is consuming more than 4TB.

The solution we're looking for is to store record's attachments outside ServiceNow keeping the possibility to download it using it's link (or something similar). This is our approach because we can't delete attachments created on the last 5 years.

Did you face something like this?

Best regards,
Lucas Simões

[Mark Roethof]

I do hear comments like legal / audit / regulations a lot at customers, though that's often a misjudgement or misunderstanding or mentioned by people who do not have the proper knowledge of ServiceNow to make such comments. The thing is people are following such comments way to quickly or are to quickly overruled by people who do not have the proper knowledge of ServiceNow. 

Obvioulsy I don't know anything about your instance. Though perhaps your instance is running Predictive Intelligence, and you might have / had the issue regarding ML Update Set attachments not automatically being cleaned up. For one of my customers, this was several hundreds of Gigabytes, one single out-of-the-box issue. Those are attachments which definitely do not have to be kept for legal / audit / regulations / etc.. And like that there are way more examples. An out-of-the-box known one, attachments which are added to a new record while the new record is not saved... floating attachment 🙂 Do you really need to keep such attachments for 5 years? No, definitely not, it's more an out-of-the-box mistake that such attachments are not immediately cleaned up. Investigating at one customer, this concerned hundreds of thousands attachments. Or what about attachments exports which are kept for 30 days (and then already deleted by the system, so not even close to 5 years), can you trim to less days if these exports are done daily to MID Servers etc and 30 days does not have any value, its just the out-of-the-box setting no one ever looked into? Or people making list exports, do you really need to keep that for legal, or is keeping meta data for such already enough? I do see people making interesting list exports, like full cmdb exports etc, such single exports can already be several Gigabytes each, all together again tens or hundreds of Gigabytes.

Etc..

Obviously this does will solve your whole sizing, though this can solve a large part of the sizing issue.

[Jason Burns3]

have the same requirements, For HR requirements we need to store video evidence from security footage, mobile pictures and video. Some evidence may be required for 7-20 years if it becomes a litigations type case. One issue is that attachment file setting is global and there's no desire to allow ITSM users to attach large files, even with attachment clean up there's additional admin on the top which has its own expense.
Are there any examples out there where videos are stored off platform in Azure blob, S3, SharePoint or an integration with a digital asset management solution?