Just wonder if anyone has tried to use Log Shipping on SQL Server 2012 collecting data from SQL Server 2008R2 and SQL Server 2005 databases? I heard it would be an easier option to implement compared to database replication.

Trying to run a project. Not sure to use Database Replication or Log Shipping. This is just a central database for reporting purposes only.

1 Answer 1


If you are using SQL Server 2012 as reporting, then you can use logshipping and configure your secondary as standby - that will allow users to read data from secondary when logs are not being restored. You can delay the restore of log files on secondary as per your needs.

Note that from lower to higher version, you are doing a one way. You wont be able to restore the sql server 2012 databases to sql server 2005 or 2008R2 easily (if you failed over).

Database transactional replication wont be supported as your subscriber (reporting server) would be on a higher version than publisher (sql server 2005 and 2008R2). See my answer here.

Also refer to SQL Server Many-to-One replication

  • Thanks Kin. I will go for Log Shipping since I require the databases for archiving and reporting only. Got to research on the hardware requirement and support issues. Wonder how easy it is if we miss 1 transaction log. I guess, I can't proceed with the subsequent job if we miss one. Data will be out of synch. Feb 25, 2016 at 0:16
  • You cannot skip tlog .. it relies on log LSNs. Just make sure no one takes ad-hoc tlog backup. Copy only backup is fine.
    – Kin Shah
    Feb 25, 2016 at 0:21
  • I do not want to skip any logs but just in case, the SQL Server job failed due to some reasons, I can't proceed further. So, the only way I can resume the entire thing is to start from full backup. Correct ? Feb 25, 2016 at 0:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.