Once an object is defined in Component Integration Services, alterations made to an object at the remote server are not made to the local proxy object definition. If an object is altered outside of Component Integration Services, the steps to correct the problem differ, depending on whether create existing table or create table was used to define the object.
To determine which method was used to define the object, run:
sp_help object_name
If the object was defined via create existing table, the following message is returned in the result set:
Object created with 'existing' option
If this message is not displayed, the object was defined via create table.
If create existing table was used to create the table in Component Integration Services:
Use drop table in Component Integration Services.
Create the table again in Component Integration Services using create existing table. This creates the table using the new version of the table on the remote server.
If the table was created in Component Integration Services using create table, you will drop the remote object when you use drop table. To prevent this, follow these steps:
Rename the table on the remote server so the table is not deleted when you use drop table.
Create a table on the remote server using the original name.
Use drop table in Component Integration Services to drop the table in Component Integration Services and on the remote server.
Rename the saved table in step 1 with its original name on the remote server.
Create the table again in Component Integration Services using create existing table.
WARNING! Do not use drop table in Component Integration Services before renaming the table on the remote server, or you will delete the table on the remote server.
A good rule to follow is to create the object on the remote server, and then execute create existing table to create the object in Component Integration Services. This enables you to correct mismatch problems with fewer steps and with no chance of deleting objects on the remote server.
