upgrade SQLSERVER 2005 to 2012 with logshipping

Posted on 2013-12-26
Last Modified: 2014-02-04
Hello ,
  I have a database  2005 R2 64 bit SQLserver (standard edition)  that is about 100G that has log shipping enable to a remote machine over the WAN  . The secondary DB is use for disaster recovery and it is in   "read-only state, Now , I would would like to upgrade to SQLServer 2012 . How would the upgrade affect my log shipping jobs?. Do I have to redo the logshipping?

It would be an issue if I have to redo the log shipping since it will take days to transfer a  backup to the remote location using our WAN

Thanks for your help
Question by:SiemensSEN
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
LVL 59

Expert Comment

by:Kevin Cross
ID: 39740394
Yes, you can upgrade log shipping configuration by upgrading the secondary server, then upgrading the primary server to SQL 2012.

Author Comment

ID: 39783575
Thanks but my database is in stand-by mode. So, according to the document it cannot be done..

Is it possible to change the stand-by to no recovery??
LVL 59

Expert Comment

by:Kevin Cross
ID: 39785298
You can change between the modes, it just does not take effect until the next log backup is restored per Microsoft's documentation.
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 39785754
Thank you so if I set the database to "no Recovery" then I can upgrade SQLSERVER.

Would this be the proper steps

1: Change the DB to no recovery
2: Pause log shipping
3: upgrade the redundant server (db's in is no recovery mode)
4: Upgrade production
5:restart log shipping

Thanks for your help
LVL 59

Accepted Solution

Kevin Cross earned 500 total points
ID: 39785797
Are you planning to fail over to the secondary server OR leave the database offline during the upgrade?

You simply can redo log shipping from scratch on the secondary server after the upgrade as an option by the way.

Anyway, I think you have the order, just remember to backup live transaction log and restore between each step if you do fail over to secondary.

Author Comment

ID: 39786230
I plan to leave the DB offline for the upgrade.

I don't want to redo the log shipping because my database id 150 GB .  To redo from scratch will require transfering the 150 GB over the WAN and that would take days. So, I would like to avoid this step if possible.

Thanks for your help

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Slowly Changing Dimension Transformation component in data task flow is very useful for us to manage and control how data changes in SSIS.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example, show how to extract insert data into a SQL Server database table using the Import/Export option and Bulk Insert.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question