Francois Koutchouk
asked on
Exchange 2010 and 2013 file formats?
My understanding is that Exchange 2007 used a proprietary and complicated ESB format, pretty much preventing external programs to upload data into mail files.
Has the situation changed with Exchange 2010 or 2013? Perhaps SQL Server as a backend?
The intent is to upload a large number of messages ("records") into the mail files of a large number of users.
Has the situation changed with Exchange 2010 or 2013? Perhaps SQL Server as a backend?
The intent is to upload a large number of messages ("records") into the mail files of a large number of users.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No SQL in Exchange 2013: http://thoughtsofanidlemind.com/2013/03/11/exchange-winfs-ofs/
ASKER
OK, ESE it is and will be. SQL provides easy ways to INSERT data in bulk. What are the options with ESE?
Yes, Users still uses Extensible Storage Engine and do not like to go with SQL.
Reason behind :
1) Due to complex SQL integration
2) Expensive license
3) highly skilled men will be required to manage the database
Conclusion : It's a bit costly and complex solution for small size business.
You can get the all featured information about ESE from here : http://tinyurl.com/msk8pdw
Reason behind :
1) Due to complex SQL integration
2) Expensive license
3) highly skilled men will be required to manage the database
Conclusion : It's a bit costly and complex solution for small size business.
You can get the all featured information about ESE from here : http://tinyurl.com/msk8pdw
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
2010 & 2013 still uses the ESE. No SQL.