Hi,

Our developers have spent few days to test on DDT and found some unclear issue as below and would like to ask for clarification:



Scenarios

----------

1.Created 1st package to create the db structure and deployment data, and run the wizard to deploy the database.

Then create another new package,2nd package with the same db structure and deployment data to deploy the database

pointing to the same db that have been created using the 1st package.Error will occured(eg:FlexHRDatabase_results.log)



2.Created package using DDT and remove any one of the database from the DDT and deploy the package again.

An error will occured if click deploy the package. This happen even though I have deleted the db deletion history.



3.Import Security table to a database using DDT.When import the security table for the 2nd time to the same database,

it will create another table for all the tables which are defined the table relationship and a message prompt out to inform

that "Relationship name: Relationship with this name already exists in the database".

Then, it will create additional new tables with same name instead of updating to the existing table.This will only occur if the table has relationship. If the table is without any relationship, it will just update to the same table without creating a duplicate new table.



Any ideas? Please advice.



Thank you

Hi,

I have gone thru DatabaseMigrator source code, found that the error below occured caused by the priority of stored proc "MessageItemsInsertOverwrite" in pre-existing database is NULL, therefore filtered by DatabaseMigrator. We never specify priority when create sp. Question is, why does it required? Anyway to not filter it?



Please advice. Thank you.



X 18/02/2009 7:52:24 PM-> An error occurred while creating the stored procedure [dbo].[MessageItemsInsertOverwrite].

X 18/02/2009 7:52:24 PM-> SqlException

X 18/02/2009 7:52:24 PM-> There is already an object named 'MessageItemsInsertOverwrite' in the database.