http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Versioning attachments is easy if you track not only versions of the document body, but also its metadata and treat the attachment files as immutable. http://ayende.com/3902/designing-a-document-database-attachments#comment6http://ayende.com/3902/designing-a-document-database-attachments#comment6Wed, 11 Mar 2009 18:46:53 GMTI certainly recommend the external storage approach. worked out well for stuff I've done in the past. http://ayende.com/3902/designing-a-document-database-attachments#comment5http://ayende.com/3902/designing-a-document-database-attachments#comment5Wed, 11 Mar 2009 16:27:50 GMTMultiple attachments, certainly. Version info? I don't think so. Permission might be an interesting problem if we store this externally http://ayende.com/3902/designing-a-document-database-attachments#comment4http://ayende.com/3902/designing-a-document-database-attachments#comment4Wed, 11 Mar 2009 16:22:31 GMTDo you want to support change tracking or version info for the attachments? Or allow multiple attachments per document? Both those are design considerations. For simplicity, I'd assume a user has the same rights on the attachment as the document, but you may think otherwise. http://ayende.com/3902/designing-a-document-database-attachments#comment3http://ayende.com/3902/designing-a-document-database-attachments#comment3Wed, 11 Mar 2009 16:19:50 GMTYou do realize that I am not going to use SQL Server as the backend, right? http://ayende.com/3902/designing-a-document-database-attachments#comment2http://ayende.com/3902/designing-a-document-database-attachments#comment2Wed, 11 Mar 2009 08:33:10 GMTHow about - [msdn.microsoft.com/en-us/library/cc949109.aspx](http://msdn.microsoft.com/en-us/library/cc949109.aspx)http://ayende.com/3902/designing-a-document-database-attachments#comment1http://ayende.com/3902/designing-a-document-database-attachments#comment1Wed, 11 Mar 2009 07:27:21 GMT