Here is a backup of the SQL db.

Here is the pkg file.

You can just post it as an attachment here on the forum if you are comfortable with that.  If not, then just PM (Private Message) me and send it to me that way.  Just package up the legacy database as a backup or mdf and then include your PKG file as well.

How do we go about getting this to you (sorry, newbie here)?  What do you require the Package definition and a backup of the legacy database to be converted?

Thanks, Aaron

Generally databases that have been updates with the DDT were initially created with the DDT...however, what you are attempting to accomplish can be done, but there are limitations (even in SQL Server) when converting certain data types from one to another.  I would have to setup the Decimal to Int scenario to see if this produces any type of error.  In some cases SQL Server Management Studio does some "smoke and mirrors" to convert certain things versus just relying on SMO.  But in response to dropping the contraints, we actually do this so that PKs and structure changes can take place.  So this would really be a matter of us getting our hands on your existing structure and the package file so that we can see what is actually going on and if there is something that we can do in the deployment phase to take some unique circumstance into account.

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