StrataFrame Forum » StrataFrame Database Deployment Toolkit » Database Deployment Toolkit (How do I?) » Error during deployment

Error during deployment

Derrick Bell — Fri, 17 Nov 2006 13:43:56 GMT

I received an error during my initial deployment. I don't know if it's significant.

Please advise.

Derrick

RE: Error during deployment

Trent L. Taylor — Fri, 17 Nov 2006 13:43:56 GMT

Good deal!

RE: Error during deployment

Derrick Bell — Fri, 17 Nov 2006 13:42:15 GMT

Yes I did delete the database in my history. I deleted the individual row I saw in history where I deleted the database, then rebuilt the package and now it worked. :cool:

RE: Error during deployment

Trent L. Taylor — Fri, 17 Nov 2006 13:37:13 GMT

Look at my previous post....I am willing to bet that you deleted a database then added that same database name bak into the DDT. This will have a history record of a delete of the database with that name.

So in this example, if I when and created another database named "appt", it will delete that database during the deployment after it has already been created. Remove this line from the history and you will be good to go.

RE: Error during deployment

Derrick Bell — Fri, 17 Nov 2006 13:33:26 GMT

However the deployment then drops the database... Guess there is a setting. Looking now

RE: Error during deployment

Derrick Bell — Fri, 17 Nov 2006 13:30:33 GMT

Fix it.. the keys in one of my tables where wrong. Just the error really didnt seem to tell me.

RE: Error during deployment

Trent L. Taylor — Fri, 17 Nov 2006 13:30:03 GMT

Look in your History...is there a delete of the database? This is another common "oops". Is so, remove the deletion record or clear your history.

RE: Error during deployment

Derrick Bell — Fri, 17 Nov 2006 13:27:27 GMT

Hmm the database is empty. And now is dropped due to the deployment process. I'm in SQLServer 2005 Express.

RE: Error during deployment

Trent L. Taylor — Fri, 17 Nov 2006 13:11:08 GMT

I cannot see the errors. You can attach the image as an attachment. But bascially, when you see errors like this, it is because something in the deployment package does not adhere to the SQL Server rules. One very common cause that people run into in the beginning is having a table with data in it and then not providing a default value (or allow null) for a new field.

But I will have to see the error in order to give any better advice.