Hi, we currently replicate data from one of our main SQL Servers (mainly transactional replication) to an independent report server. Our main server is a cluster joined to a SAN. The report server is fast becoming unfit for purpose so we are looking to purchase new hardware and also hook the new report server up to the SAN.
My question is, should we continue to use Replication between our main server and report server, even though the discs will reside on the same hardware? Is there a 'better' way to make the data available for reporting other than using Replication?
My initial suspicion is that Replication will remain but I'd just like to throw this question out to see what other DBA's may have done in this situation.
Probably only useful if you have control of when reports are run and are happy with snapshots of data.
========================================== Cursors are useful if you don't know sql. SSIS can be used in a similar way. Beer is not cold and it isn't fizzy.
Thanks Nigel. Snapshots are an Enterprise only feature and we're running Standard. I don't suppose there is anything wrong with keeping Replication, it just feels odd when the discs are on the same metal. It should be quick anyway, without any network latency etc......
Can still be slow if you update every row of a large table. If you've already got that set up and working happily it's probably more effort to change than it's worth - unless there's another reason.
========================================== Cursors are useful if you don't know sql. SSIS can be used in a similar way. Beer is not cold and it isn't fizzy.
New Approach to Replication?
Posted - 06/15/2012 : 06:00:56
