Post reply

Replicating data from 2014 to 2005 - temporarily

  • January 4, 2016 at 11:42 am

    #323695

    Hi

    I will be installing a new database sql 2014 system, which is based on our current 2005 database system.

    The new system will be on a completely new infrastructure when we go live, leaving the current infrastructure available for rollback should we encounter any issues.

    The business requires that a rollback option be available for 2 weeks minimum. Therefore in the event of a disaster scenario we would be required to switch back to the 2005 database system. So the challenge I have is replicating the data upon going live with the 2014 database system.

    I am looking for a way to replicate the data (not necessarily the schema) from the 2014 system to the 2005 system.

    I am not really a fan of SQL Server Replication and my preference is not to use this. My understanding is that this is not an option for us anyway due to the versions being too far apart, and therefore not supported.

    I want to reach out to the community to find out if any tools are available to achieve this type of replication.

    It may be possible for us to implement a schema change freeze if this helps in finding the right solution.

    Please can you advise what options are available to us, if any? Or should we look to develop a bespoke system internally?

    Are you aware of any Microsoft partners that might achieve this for us through a solution already developed?

    Thanks in advance for any advice.

    Joe

  • January 4, 2016 at 2:57 pm

    #1849379

    Quick question, what is the recovery window's size, that is how much time can you spend on reverting?

    😎

  • January 4, 2016 at 3:47 pm

    #1849399

    I would say the business would allow up to 4 hours with minimal data loss. Obviously they'd want this to be as small as possible but 4 hours is the maximum they would accept.

  • January 4, 2016 at 3:57 pm

    #1849402

    That makes things somewhat easier, how complex are the schemas and what is the cardinality?

    😎

  • January 5, 2016 at 2:07 am

    #1849462

    The schema is quite simple with very few relationships and constraints (apart from most tables having a PK).

    Cardinality is high on critical tables... and gets lower with non-critical tables.

  • January 5, 2016 at 6:20 am

    #1849497

    Have you considered using Change Tracking?

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply