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 786091
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T20:59:00+00:00 2026-05-14T20:59:00+00:00

I am new to SSIS, so please bear with me. I created an Integration

  • 0

I am new to SSIS, so please bear with me.

I created an Integration Services Project for SQL Server 2008 to import data from an old db to a new one. One of the things I need to do is import data from two old source tables into one new destination table.

What is the best way to do this?

I can easily see the results I want with a simple inner join query using tsql, but am not having any luck using the SSIS package. My current approach is a three step process:

  1. Add OLE DB Source component that pulls all columns from my first source table
  2. Add a Lookup component, which is the next step after my OLE DB Source component. In this I query the second source table ‘using the results of a sql query’ that returns no nulls, then drag the foreign key id from the ‘available input columns’ to the primary key in the available lookup columns. I also check the checkboxes in ‘available input columns’ to add 2 more columns.
  3. Add OLE DB Destination, pointed to my destination table.

This process fails at the first step, not at the lookup step, and fails with the error “Row yielded no match during lookup”. The foreign key cannot be null, and obviously the primary key can’t either. I used a SQL statement in step to so I could make sure I don’t get any null date values in the columns (there were a few) but I am still getting the error. If I output the first step failure path to a Flat File Destination, I get an empty CSV (watching in debug mode says ~600k records go into the flat file).

I am pretty stumped at this point and this seems like it should be super easy task. I have scoured the web for answers, and found this link that sounds like the same exact problem I am having, but changing the cache setting didn’t help.

Help appreciated!

  • 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-14T20:59:00+00:00Added an answer on May 14, 2026 at 8:59 pm

    It sounds like you have a mismatch in the lookup. I’d hand run the queries and verify that tha both OLE DB SOurce has no null foriegn keys; and that each foreign-key matches something in the lookup table.

    There is a simpler approach here. Use your inner join query you mentioned in the OLE DB SOurce. Don’t use the table select, provide your SQL query with the join. This let’s the SQL Server do all of the heavy lifting of the join and then SSIS can do the transferring.

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

Sidebar

Related Questions

I am new to using SSIS 2008 and am currently working on migrating data
I have an SSIS 2008 package that reads data from an Access database (OLEDB
I'm very new to SSIS, so please bear with me. A developer gave me
I'm currently creating an SSIS job that will pull picture data from a SQL
I have an SSIS package that exports data from a table on a SQL
Working in SQL Server 2008. My first stab at an SSIS script and I
I have powershell version 2.0.0.1082 on my server. I want to import data from
Can I use the new SQL Server Data Tools that come with SQL Server
I am very new to SSIS, looking at a package already created by someone
I have an SSIS exportation package that is used to export data from an

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.