Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3852142
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 19, 20262026-05-19T17:16:19+00:00 2026-05-19T17:16:19+00:00

I’ve got an Employees table on a SQL 2005 server, and a nearly-identical Employees

  • 0

I’ve got an Employees table on a SQL 2005 server, and a nearly-identical Employees table on a SQL 2008 server (the servers are not linked). One table is in the production database, and the other is in a dev database. I have to pull data from production into the dev database on a scheduled basis and I’m using SSIS to build a package to do this.

I need to set up an SSIS package that will:

  1. Compare the two tables to determine if they are not ‘synched’. That is, to see if the prod table has rows that are not yet in the dev table.
  2. Only if necessary–update the dev table with just the new rows from the prod table.

I’ve muddled around with a few ways of doing this, but I’m looking for a more elegant solution than what I’ve been able to come up with. What’s the best way to do this?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-19T17:16:20+00:00Added an answer on May 19, 2026 at 5:16 pm

    The simplest way of achieving this (although possibly not the most efficient depending on your data volumes) is to feed the Production source data into a Lookup Task which is based on the Development data, looking up on the PK column(s). Set the rows that do not match (or fail if using 2005) to be redirected to a new flow – you can then use this to feed back into your Development table using an OleDb Destination.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.