MS SQL server 2005 sequences for DD? big issues

System

in this past w/ oracle it was easy to use DD w/ oracle sequences as a primary key, but w/ sql server we r having the following issues:

Our iwov DD table has an IDENTITY field called ID as the primary key

1. This is maintained and inserted by the DB itself, we cannot pass it from the DCT.
2. Since this is a primary key, DD won’t work unless it gets a value for this field from DCR.
3. Now this primary key column is used as a Foreign key to establish a join between the events and their location [in another table]. DD needs us to specify this foreign key relation in the config file for deployments to happen in both tables.

The reasons we chose to request the removal of identity field are:

1. The identity fields happens to be the primary key as well OD doesn’t support it. [as per the release notes].
2. The Values of the Identity field would not be available to us until the insert to the main table is complete. We will need a script to get this value from database. Then we will be forced to update the secondary table externally using another Perl script through a separate external task in the workflow.
3. Also, if we update the main table using OD and later update the location records through another IPL , there is no transactional deployment, we will have to think a logic for the rollbacks, which are usually automated and managed by DD itself