One possibility I thought of was...

That's pretty cool, thank you.

Same link as mine;-)

Have a look here[/url] - I'm sure you can adapt it to your needs.

What do you want to happen?

1) Do you want to delete all the rows and re-load them? If yes, just truncate the destination table before doing the load.

2) Or not...

nikishh9 (5/19/2011)

---

Hi All,

i load the data from Staging database to Poststaging but when run package two time at that time i got same rows two time or if i run...

Can you give some background on what you are doing - what method are you using to run DTEXEC?

And your secure alternative solution is?

raj_shekar2005 (5/18/2011)

---

I have OLEDB source for Flat File destination. Flat file destination is mapped to flat file connection manager. My source has arround 5 columns of different lengths. My report...

I'm afraid it is a bit 🙂 Nonetheless, glad you got there in the end!

Using a stored proc as the source for your report makes this task easy enough to run on the server.

I'll second that - a simple method which avoids sending unwanted data across the network.

You can do it in a single package - but you'll need 2 dataflows and some precedence logic to control which is executed. You may also have to set delayvalidation...

SSIS can't easily accommodate this sort of requirement. If it's only ever one of two formats, you'll just need two data sources and some conditional logic to force processing down...

When it come to mapping of SSIS data type and SQL Server datatype then nchar, nvarchar, sql_variant, xml will be mapped directly to DT_WSTR (SSIS data type). Any mapping given...