Export/Import BizTalk Parties with Database functions

Christian has already explained how to export and import large amounts of BizTalk parties with BindingImport. Now, we were thinking of exporting the BizTalk parties directly from one BizTalkMgmtDb to a new server without BizTalk parties. You can do this in six steps:

1. Check wether there are no parties yet saved on the target server (check bts_party)
2. Temporarily disable the identity flag for the primary key columns n_id of the tables bts_party and bts_party_alias on the target database.
   
3. Copy the table bts_party from the source system to the target database (you can't copy both tables in one step due to references' integrity).
4. Enable the identity flag for column n_id in table bts_party on the target database.
5. Copy the table bts_party_alias from the source system to the target database.
6. Enable the identity flag for column n_id in table bts_party_alias on the target database.

There are also other party tables such as bts_party_sendport, bts_enlistedparty, bts_enlistedparty_operation_mapping, and bts_enlistedparty_port_mapping. However, those connect parties to sendports, role links, mappings and ports, and should be rather configured than directly changed inside the database.

If you also want to adapt more EDIFACT configurations, you have to migrate the tables that start with "EdiPartner", too!