<p>I have an SSIS package that copies the data in a table from one SQL Server 2005 to another SQL Server 2005.  I do this with a "Data Flow" task.  In the package config file I expose the destination table name.</p>

<p>Problem is when I change the destination table name in the config file (via notepad) I get the following error "vs_needsnewmetadata".  I think I understand the problem... the destination table column mapping is fixed when I first set up the package.</p>

<p>Question:  what's the easiest way to do the above with an ssis package?  </p>

<p>I've read online about setting up the metadata programmatically and all but I'd like to avoid this.  Also I wrote a C# console app that does everything just fine... all tables etc are specified in the app.config ... but apparently this solution isn't good enough.</p>

If all you are doing is copying data from one SQL2005 server to another I would just create a Linked Server and use a stored proc to copy the data. An SSIS package is overkill.
How to Create  linked server
Once the linked server is created you would just program something like...
```
```
INSERT INTO server1.dbo.database1.table1(id,name)
SELECT id, name FROM server2.dbo.database1.table1
```
```
As far the SSIS package I have always had to reopen and rebuild the package so that the meta data gets updated when modifying the tables column properties.