Hi,

Pls refer to the following errors that I got when I deploy a package to SQL Server using Database Deployment Wizard. These errors only occured when I run the wizard for the 2nd time but it works fine for the 1st time without any error.

Senarioes

1. The database already exist at SQL Server(eg:VfsMain) and I run the wizard for the 2nd time using the same package but I renamed the Database Name on Server to another name(eg:VfsMain2). I hit this error as per attached (FlexHRDatabase_results4.rtf).

2. The database already exist at SQL Server and I run the wizard again for the 2nd time using the same package. I hit this error as per attached (FlexHRDatabase_results1.rtf).

Pls kindly advice.Thanks.

Hi,

Thank you for you valuable information.

If so, I might need to keep all history, then it would be very very huge in future. Beside, it could be confused as developers might do something wrong in DDT and revert them back and etc. If all of this stored in history, it might cause unexpected problem, would it?



I was thinking DDT would compare customer db and generate the upgrade script on the fly during upgrade based on the package generated. Shall SF team confirm on this? I know RedGate has a utility for this, but it required us to restore our latest db in order to work which is not our preference. Shipping XML/package is the way.



Please advice. Urgent!

Thank you