Lync 2013 SQL versus Exchange Archiving

Our organization has setup an internal lab for Lync and is trying to decide what the best option would be for deploying archiving with Lync and what the pros vs cons are.

We currently have one Lync 2013 FE Server and an Exchange 2010 server, which I already know does not support archiving. Would it be best to deploy a SQL server for archiving or upgrade Exchange 2010 to 2013? We can do either, but was is the recommended approach and best practice/pros/cons?

I was planning on utilizing SQL server as the preferred for approach and so we don't have to upgrade Exchange -- just seems easier and will keep any additional load off the Exchange server and once deployed to a production environment. 


June 30th, 2014 12:17pm

Archiving to Exchange 2013 gives you some additional features that archiving to SQL doesn't have like:

Data is indexed by Exchange search Engine and can be discovered using Exchange Discovery tools or SharePoint Discovery Center.


Free Windows Admin Tool Kit Click here and download it now
June 30th, 2014 1:01pm

Agree with Michael.

This data stored in Archiving database is not searchable, but it can be exported to formats that are searchable using other tools.

You can check the difference between these two archiving options at

July 1st, 2014 2:22am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics