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.
LVL 2
Francois KoutchoukCTOAsked:
Who is Participating?
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
The problem you have is that Exchange works at the mailbox level. Everything is built around importing content in to a mailbox.
If you have a large amount of content, then the most efficient way to import it is through Outlook (without using third party tools).
Otherwise it is a third party tool which will do the import for you, again in to the mailbox. You don't manipulate the database at an item level at all.

Therefore it depends on what format the source material is in. Ideally its original source, not whatever it has been exported in to. If it is mail content for example, it is far easier to export it from the mail server directly, or the client holding the content. Exporting each item to a file makes things a lot more difficult.

Simon.
0
 
imkotteesSenior Messaging EngineerCommented:
as per my knowledge nothing has changed.

2010 & 2013 still uses the ESE. No SQL.
0
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
Exchange will never use SQL.

http://blogs.technet.com/b/exchange/archive/2009/07/16/3407812.aspx

For importing content you will need to use a third party tool, or go through Outlook.

Simon.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Stelian StanNetwork AdministratorCommented:
0
 
Francois KoutchoukCTOAuthor Commented:
OK, ESE it is and will be.   SQL provides easy ways to INSERT data in bulk.  What are the options with ESE?
0
 
michaelalphiCommented:
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
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.