SSIS 2005: "Append rows to the destination table" is greyed out. Why?

Question

In SQL Server 2005, Import Data (SSIS), my desire is to import a text file and have it append to an existing table. The first time through the wizard on the Column Mappings step I swear the Append rows to the destination table radio button was enabled. But, now, it's disabled (grey) and even re-starting the wizard won't cause it to re-enable.

Is there some secret/magic I don't know about? How do I get that option to re-enable so that I can append (rather than Create destination table)?

Solution 1

In my experience, if the table you're importing into doesn't exist at the time you're going through the "SSIS Import and Export Wizard", you won't have the option to Append; if the table does exist at the time you're going through the wizard, the option is available.

If you do choose the "Create table" option, the wizard just builds the SSIS package with an Execute SQL task that builds the table prior to the data flow that loads the data. So, you can always just remove the task in the resulting package and you'll get "Append" by default.

Solution 2

I know what you're missing... because I once missed it too!

From the screen, "Select Source Tables and Views",
there is a "destination" drop-down menu on the right side.

Select your table from this drop-down,
then click on the "Edit Mappings" button.

Now the append option will be enabled!

Solution 3

The name of the table must be preceded with schema name ("dbo."). Otherwise the wizard didn't find it in my case.

Comments

[anton.burger]

Just what I was missing too. Thanks!

[jlo-gmail]

This was the clue! In my case the table names had different cases.

[CareTaker22]

Thanks! This was my issue. "the table you're importing into doesn't exist at the time". I didn't refresh sql server after I used code first migrations with EF6 so my tables didn't exist yet.

[DontFretBrett]

Same issue here. I suppose one idea, a little crazy but hear me out. What if, it's a big IF, the tool had a check if the destination has a matching schema.table as the source and it pre-populates the destination with the matching value. Nah nvm. Stupid