Let's say 3 development teams (1 at customer's site, and 2 consultants) with no LAN or VPN to join them, only mail or ftp. Each team owns licences for SF and DDT, and can create deployment packages to apply on customer's SQL Servers (and of course on SQL Servers for tests at consultant's office)

When I receive customer's package, I can import it in a profile and deploy it from that profile. From another profile, I generate a package, and customer may deploy this package I'll send him. And of course, each deployment delete and  replace what was locally written

How could I merge the 2 packages into a single, in order to see all modifications in a single profile? from within DDT? with a merge replication in SQL Server? with a versionning product (Visual SourceSafe or another one)?

Thanks in advance for all advice.

We have 3 teams, working on the same application/database:

• team1 is on the customer's site, and may modify structures, adding new tables and new columns to existing tables. They know all the industrial processes, and may "translate" in data structures new requirements asked by end-users
  Team1 is the origin of all DDT packages
• team2 receives DDT package from Team1, and may modify it, mainly by checking indexes, constraints, and foreing keys, and adding UDF and SP to database
  Team2 uses this DDT as a source for all BO: team2 writes BO library
• team3 is in charge of all presentation layer design, and receives DDT and BO library from team2. Team3 mays sometimes add few modifs on BO, if required for presentation layer.

To prevent overwriting, it seem that each team needs 3 DDT profiles. For instance, I am team2 (I am really team2 ).
I receive a package from team1, and imports it in profile "fromTeam1", then generate a package in the same profile, and import it in "My Profile".
Working in "My Profile", saving changes in my local Strataframe database, and finally I generate a pkg file to send to team1 and team3.

Do you think we need a database for each profile?