Also 'beleive' and 'varibble' 🙂

Surely, when you start getting to the realms of datasets with more than 65k rows, a spreadsheet is not the right repository. You need a database solution (Access maybe) or...

Please respond to Pradeep Adiga's posts - why is that not what you want?

coalesce (8/1/2010)

---

I'm not...

Of course you can.

Create a new Integration Services project, then right-click SSIS Packages in Solution Explorer and 'Add Existing Package.'

Then you're good to go.

Have a look here[/url].

You should be able to set the TransactionOption property of your DF to 'Required' to get the behaviour you require.

I still think your first answer was better (Excel 2007). Even better than that, however,...

Instead of using a File System task, use a script task containing appropriate code. It works much better, in my experience and requires just three or four lines of code.

OK ... may I ask what 'Transfer SQL Server Objects' gives you that a dataflow task does not? Just wondering why you went down this road.

Sure - do a multicast to all of the tables you need to update ...

Why not just copy the data you require? Deleting & recreating table objects repeatedly seems a little inefficient.

Is this because you have the same data in multiple tables (ie, redundant data)?

If there is no delimiter, it is, by definition, not a CSV file.

It's a fixed-width file and you can use SSIS to import it and break it into its constituent...

ameda16 (7/27/2010)

---

an idea: use no cashing instead of full precaching, the default caching type

No caching, in which the reference dataset is accessed by each row in the rowset. To...

So your DF contains duplicates? Why not get rid of them early in the DF and save yourself the trouble? If not, what happens when the lookup is successful? How...