Change your OLE DB Destination from what is now the final destination table to a staging table.  Remove the Data Conversion transformation, so that you're copying direct from the file...

It's so simple that you don't even need to use SSIS.  You can use bcp or BULK INSERT (or SSIS if you insist, or if it's part of a larger...

If you run your restore through SSMS, it'll run as the SQL Server service account.  If you do it as part of a job step, it'll use the SQL Server...

Have a look at this article, and see whether you can get it working with CHAR(10) + CHAR(13) as a delimiter.

John

Steve is right.  DDL and data would make our task much easier.  Here's a guess in the absence thereof. Have a look at this and at what Thom posted -...

Is there anything in the restorehistory table in msdb?  Maybe not, I suspect - it's not nearly as useful as the backup tables.

John

It's harmless, according to this.  Are you actually using SQL Server 2012?

John

One thing that combines the best of both worlds is to test for existence, and create a stub object if it doesn't exist.  After that, everything is an ALTER.

My advice, if you have any control over this, is to avoid this kind of design.  You've seen how difficult it is to write even the simplest query.  And what...

You're using an Excel Source in your Data Flow task, right?  Why not choose SQL Command for your Data access mode, and then you can write a query that will...