Recently, when I discovered that a package was not able to run if it tries to import a VFP table which already exists in the SQL Server database, I decided that removing the tables from the database would work. This is ok as long as I do not do any change to the SQL Server database. But, of course, this is no longer applicable as I started to adjust the design of the database. So, for example, I have identified identify fields. So, if I remove the table from the database in order to be able to run my package, I am loosing all those settings.

Is there a way to run a package by preserving the table in the database? If not, this would mean I would have to tell the package what fields are used for identity. In such a case, anyone would know how to do that in the package?