February 22, 2016 at 10:38 pm
Hi DBAs,
Just wonder anyone tried to use Log Shipping on MSSQL 2012 collecting data from MSSQL 2008R2 and MSSQL 2005 databases ?
If you do, what's the challenges you encounter ?
Trying to run a project. Not sure to use Database Replication or Log Shipping. This is just a central database for reporting purposes only.
Would like to hear your thoughts. Thanks.
February 22, 2016 at 11:04 pm
Hi,
if you use replication, you are able to decide, which table, view or something else should be replicated.
If you use logshipping, the entire database will be synchronized.
Kind regards,
Andreas
February 23, 2016 at 5:30 am
davidku (2/22/2016)
Hi DBAs,Just wonder anyone tried to use Log Shipping on MSSQL 2012 collecting data from MSSQL 2008R2 and MSSQL 2005 databases ?
If you do, what's the challenges you encounter ?
Trying to run a project. Not sure to use Database Replication or Log Shipping. This is just a central database for reporting purposes only.
Would like to hear your thoughts. Thanks.
You can log ship from 2005 or 2008 to 2012 but the data will not be accessible, you will not be able to put the 2012 database into standby\readonly mode, I'm assuming you'll want access to the data
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 23, 2016 at 9:04 am
To add on with Perry, the upgrade/recovery won't run until the database comes online, so you're stuck. This only really makes sense in an upgrade scenario.
You need to use replication to move this data in a way that's usable on the second server.
February 23, 2016 at 9:49 am
I had issues log shipping from 2005 to 2012. I believe the official limitation is two major versions. I.E. 2005 + 2 major versions is 2008 R2.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply