It sounds like you're covering all your bases... not sure what's going on here.

How are you setting your variable value - is it set on creation (in the Variables window...

Yes, you are correct that the database name would be left blank if you're using a variable.

Can you check the SourceConnection to make sure you have a valid source specified?

Check the case - you had previously noted the name of the variable was InDatabase, but your most recent post shows it as Indatabase. SSIS is case sensitive for...

You're right that the conditional split could be used in some cases, but when you have outputs with differing numbers of columns, the script component would be ideal.

When you say "raw file", are you referring to a file created by the Raw File Destination in SSIS? If so, you can't import this using BCP - it's...

I've seen this issue pop up before on mapped drives. They are deceptively easy to use but almost always cause problems later.

Quinn,

Are you using a SQL Server Destination to write the data to your SQL Server database? If so, I recommend changing to an OleDB Destination. The SQL Server...

As indicated by your posted error message, there are duplicates in your reference data used for the lookup. You can do one of two things to fix this: ...

Yes, you could do this with a Script Component. However, if you allow incoming data files to update your metadata, you run the risk of causing some much bigger...

It sounds like you've got a mismatch in your variable character types between the source and destination. SSIS won't implicitly change a VARCHAR (ASCII) to NVARCHAR (Unicode) or vice...

I agree with GSquared in that, if the UPDATE is the only thing you're doing, one or two SQL statements could be used for this.

If you need to include this...

When you install SQL Server 2005/2008, you can also install the Business Intelligence Developer Studio (BIDS) environment, which is essentially a set of templates that allow you to open and...

Retrieve fewer columns by using SELECT [column1], [column2], etc, rather than SELECT *. Appropriate indexes will help as well.

For better answers to your questions, include more detail about your...

If you execute an SSIS package from the BIDS designer on a workstation that has the SSIS runtime installed and running, the package will be run using the local SSIS...

You should remove the line that reads:

OReader.NextResult()

You're actually duplicating the call your making with the reader.Read() at the top of the loop, which results in skipping rows within your data.

hth,

Tim