>You can use an Identity field. BUT IMHO using an integer field as PK is not a good idea (I'm in use GUID as PK camp).

The question was how to adjust the package to know about it. It is, of course, simple to go in each table after in SQL Server and change the type. But, I don't want to have to do that for 120 tables. I would like the package to be smart enough to handle that at process time.

Also, this is in regards to that and not debating what field type should be used for a primary key. But, thanks anyway