|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Monday, March 11, 2013 8:52 AM
Points: 65,
Visits: 321
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Thursday, May 16, 2013 4:05 AM
Points: 318,
Visits: 640
|
|
Great article, definitely one for the favourites file. The screenshots could with being bigger though, there were a few where the details in them were unreadable.
Barney
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Sunday, May 19, 2013 3:38 PM
Points: 23,
Visits: 563
|
|
| Being as the images are so small - perhaps you could upload the package, that would allow people to check their results with the package you created.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, April 08, 2013 2:42 PM
Points: 1,
Visits: 86
|
|
| In my processing we recieve many files like this, for the part where your moving the non lookupvalues to another table, I typically deal with them by adding them to the lookup table in the error output then merge the rows so you get the new lookup value.
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Monday, March 11, 2013 8:52 AM
Points: 65,
Visits: 321
|
|
| I agree about the screen shots, don't know what happened during the upload to the site. Here's a link to a pdf.
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Friday, April 19, 2013 4:50 AM
Points: 109,
Visits: 114
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Today @ 6:46 AM
Points: 328,
Visits: 1,851
|
|
SQL Server Destinations
I'm not sure that using SQL Server Destinations is a good idea as the target server has to be local to the package
|
|
|
|