2 added 244 characters in body
source | link

I have a SQL Server 2012 Std cluster that has a lot of writes going on. We'd like to offload some of the reporting to a separate (2012 Std) VM. It can be around 24 hours out of date.

I think log shipping is probably a good approach but I'm concerned I won't be able to compress the tlogs (they'll be big). My question is, can I manually set up log-shipping, essentially leaving the primary untouched and just restore 24 hours worth of transactions on the secondary each day - whilst still being able to read from the secondary during the day?

EDIT: After doing some testing and with the help from users here, it looks like I can just "manually" restore 24 hours' worth of backups each day by going SINGLE_USER then restoring all the tlogs WITH STANDBY, essentially log shipping but without touching the primary at all.

I have a SQL Server 2012 Std cluster that has a lot of writes going on. We'd like to offload some of the reporting to a separate (2012 Std) VM. It can be around 24 hours out of date.

I think log shipping is probably a good approach but I'm concerned I won't be able to compress the tlogs (they'll be big). My question is, can I manually set up log-shipping, essentially leaving the primary untouched and just restore 24 hours worth of transactions on the secondary each day - whilst still being able to read from the secondary during the day?

I have a SQL Server 2012 Std cluster that has a lot of writes going on. We'd like to offload some of the reporting to a separate (2012 Std) VM. It can be around 24 hours out of date.

I think log shipping is probably a good approach but I'm concerned I won't be able to compress the tlogs (they'll be big). My question is, can I manually set up log-shipping, essentially leaving the primary untouched and just restore 24 hours worth of transactions on the secondary each day - whilst still being able to read from the secondary during the day?

EDIT: After doing some testing and with the help from users here, it looks like I can just "manually" restore 24 hours' worth of backups each day by going SINGLE_USER then restoring all the tlogs WITH STANDBY, essentially log shipping but without touching the primary at all.

1
source | link

Secondary reporting SQL Server

I have a SQL Server 2012 Std cluster that has a lot of writes going on. We'd like to offload some of the reporting to a separate (2012 Std) VM. It can be around 24 hours out of date.

I think log shipping is probably a good approach but I'm concerned I won't be able to compress the tlogs (they'll be big). My question is, can I manually set up log-shipping, essentially leaving the primary untouched and just restore 24 hours worth of transactions on the secondary each day - whilst still being able to read from the secondary during the day?