Single instance storage is a feature of Exchange that we haven't talked about much since the 1990s. We made some changes to how single-instancing works in Exchange 2007, so I wanted to give everyone ...
Updated Jul 01, 2019
Version 2.0
Blog Post
@Nick
Thanks for your time and clarity.
Interesting that whole message SIS is still a delivery enhancement. As a point of reference, I worked for KVS as a Technical Evangelist, prior to that I worked with NT/NTDS and Exchange DS/IS from 1995-? in architect and product management roles, enough posturing for now. With that in mind, your points about attachment separation leave me in a lurch.
The lurch I'm left in revolves around the future of attachment separation and APIs. Will there be an API to access those attachments? For example, using the API I would like to move the attachment to SharePoint. In the objects place I would like to leave a SharePoint or /other/ address. This address would be called by the Exchange MAPI provider in Outlook when the attachment is requested by a user/application.
One could retain the message objects, but offload the storage expensive attachments to SharePoint or a base file system, where they likely belong. There would be some minor changes to the categorizer/transport sinks to accommodate sending attachments out of an organization. However, in my example above, attachment offloading to SharePoint or /OTHER/ would occur over time. Therefore, the most recent email wouldn't be subjected the the process intensive recall of offline attachments during outbound email delivery, etc.
I'm not looking for "use email archiving for mailbox management (with stubs)" as an answer. because. its. not. (there is a better option for STUBS, especially if the Outlook/Exchange MAPI transport/storage provider had a plug-in option, i.e. indexing)
So, what are the prospects for an API to start working with the separated attachments? On a side note, is there PerfMon object/counter for Message/Attachment SIS?
Joshua
Thanks for your time and clarity.
Interesting that whole message SIS is still a delivery enhancement. As a point of reference, I worked for KVS as a Technical Evangelist, prior to that I worked with NT/NTDS and Exchange DS/IS from 1995-? in architect and product management roles, enough posturing for now. With that in mind, your points about attachment separation leave me in a lurch.
The lurch I'm left in revolves around the future of attachment separation and APIs. Will there be an API to access those attachments? For example, using the API I would like to move the attachment to SharePoint. In the objects place I would like to leave a SharePoint or /other/ address. This address would be called by the Exchange MAPI provider in Outlook when the attachment is requested by a user/application.
One could retain the message objects, but offload the storage expensive attachments to SharePoint or a base file system, where they likely belong. There would be some minor changes to the categorizer/transport sinks to accommodate sending attachments out of an organization. However, in my example above, attachment offloading to SharePoint or /OTHER/ would occur over time. Therefore, the most recent email wouldn't be subjected the the process intensive recall of offline attachments during outbound email delivery, etc.
I'm not looking for "use email archiving for mailbox management (with stubs)" as an answer. because. its. not. (there is a better option for STUBS, especially if the Outlook/Exchange MAPI transport/storage provider had a plug-in option, i.e. indexing)
So, what are the prospects for an API to start working with the separated attachments? On a side note, is there PerfMon object/counter for Message/Attachment SIS?
Joshua