We have an ERP software package with a number of database definiitons that we are hoping to correct. We're trying to use the Database Deployment Toolkit to deploy new definitions to our legacy databases used in the field by our customers.  Our first attempt at converting the database schema to an updated schema has not been very sucessful.  Primarily, one of the issues that is trying to be corrected is converting PK datatypes from Decimal(10,0) to Int.  It appears based on the log error messages that the PK constraints are not dropped prior to the type change being applied. 

Is this something that the tool is meant to support?

Thanks,

Aaron

This issue has nothing to do with you decimal to integer stuff.  You have deletions in your Object Historh which is removing file groups and/or databases which is causing the issue.  In the DDT, we keep up with a history of the deletions and renames.  So if you deleted a file group, database, table, or renamed a field and then named it back, you can run into this type of error.  Check the Object Name History and remove anything that is not supposed to be there.

In the next update, the DDT is going to have a checking mechanism to warn you about this type of thing since so many people have a hard time with this.  It is a required component as it allows structures to be updated from version 1 to 3 in a single step withou having to load multiple updates sequentially.  But this is one of those side effects.

Also, be sure to get the most recent version of 1.6.5 as there were quite a few enhancements made to it the other day (there will be more in the next update as well). http://forum.strataframe.net/FindPost14258.aspx