Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
vamsimahi
Starting Member
29 Posts |
 Posted - 2008-09-17 : 11:08:58
|
| I have a data flow task, which extracts the data from a flatfile source (.csv file) does some transformation (derived column) and loads the data into my OLEDB destination(SQL table).As of now, its works fine. But we do expect some bad data in our souce files. So, I want to separate good data and bad data into two separate SQL tables.How can I modify my package and how is the strucuture of my bad data table going to be ? |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-17 : 11:23:01
|
| Can you explain what bad data means in your scenerio? Use Lookup task to direct bad data to other table. |
 |
|
|
vamsimahi
Starting Member
29 Posts |
Posted - 2008-09-17 : 12:51:24
|
| I am not sure where the data is going to be bad, I mean in which field. I want the good data into my Destination table and redirect the bad rows into the Table for bad data. I don't know how the Table for bad data going to be. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-09-17 : 12:57:09
|
| Can you give scenerio or sample data for bad data so we can explain clearly? |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-09-17 : 12:58:09
|
quote:
Originally posted by vamsimahi
I am not sure where the data is going to be bad, I mean in which field. I want the good data into my Destination table and redirect the bad rows into the Table for bad data. I don't know how the Table for bad data going to be.
without knowing what is good data and bad data in your context, how will you decide which ones to be redirected? What according to you can be bad data? do you have any reference? |
|
|
|
|
|
|
separating good and bad data from flatfile source