Post reply

Data update from one database to another database (Insert and Update both)

  • December 24, 2012 at 3:13 am

    #266543

    Hi,

    I have 2 database tables.

    1) From Production

    2) From Dev.

    The task is to move the data from Production to Dev Server.

    But the issues is that when the data is already exist then it will update else if no record exist in Dev Server then it will insert.

    Existence of Data is checked through one column.

    please respond asap if you have any good solution.

  • December 24, 2012 at 6:33 am

    #1571266

    This is pretty straight forward in SSIS

    In a dataflow,

    -create a source from your prod server.

    -Lookup records on your dev server. In SQL Server 2005 I believe you have to set it to ignore the failure

    -Create a conditional split that compares the value in your source (prod) to the value you target (dev)

    -In the split where they match send the data to a staging table

    -In the split where they don't match send the data to be inserted to your target.

    After the data flow runs, build an Execute SQL Task that takes the matched data from your staging table and updated the target (dev) data.

  • December 24, 2012 at 9:46 am

    #1571313

    thanks. its working in some of my test sample data.

  • December 26, 2012 at 7:45 am

    #1571569

    Daniel Bowlin (12/24/2012)

    This is pretty straight forward in SSIS

    In a dataflow,

    -create a source from your prod server.

    -Lookup records on your dev server. In SQL Server 2005 I believe you have to set it to ignore the failure

    -Create a conditional split that compares the value in your source (prod) to the value you target (dev)

    -In the split where they match send the data to a staging table

    -In the split where they don't match send the data to be inserted to your target.

    After the data flow runs, build an Execute SQL Task that takes the matched data from your staging table and updated the target (dev) data.

    A couple of revisions

    In the no match, that actually would get sent to an update process, not insert

    There should be a null in some of your lookup values, the nulls would be the new records that should be inserted.

  • December 26, 2012 at 8:45 am

    #1571584

    Thanks a lot.

  • December 30, 2012 at 6:44 pm

    #1572419

    Since you just want to duplicate the table, you might find it quicker and simpler to just bulk reload the entire table, depending on data volume.

  • December 31, 2012 at 9:10 am

    #1572527

    Have you considered replication? That might be an option.

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

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