We have a transactional database and a reporting database that are kept in sync using transactional replication. The transactional database (source) only retains three months of data, but the reporting database (destination) contains much more data.
Generally, when there is a replication break down, our administrators take a snapshot of the source database and restore it at the destination. This will not work in this case however because the source only has 3 months of data, not all of it.
Because of this process, our administrators are requesting we don't use replication between the two databases, but instead write custom stored procedures run by SSIS jobs that run every half hour to move the data.
I'm not an expert in replication but I feel there must be a better way to accomplish this. How can we recover from a replication failure when the source database only has a subset of the data?
SQL Server 2012 Enterprise