Hi,

I´m using DatabaseMigrator to deploy DB changes to a lot customers databases in the same server.
The problem is:
All commands are processed every time that I run the program, but I realized that it rans the same command already proccessed before like:

• 12/03/2010 09:56:02 -> The relationship 'FK_tb_ped_compra_tb_item_pec' was created successfully.
• 12/03/2010 09:56:09 -> The relationship 'FK_tb_tit_pag_tb_tit_pag_ccusto' was created successfully.
• 12/03/2010 09:56:09 -> The relationship 'FK_tb_tit_pag_tb_tit_pag_proj' was created successfully.
• 12/03/2010 09:52:50 -> The table 'tb_tit_rec' was successfully altered.

Other thing:

• 12/03/2010 09:52:42 -> The relationship 'FK_tb_tit_rec_tb_tit_rec_ccusto' was successfully dropped.

If DatabaseMigrator drop my FKs, what is happen if I run it over a DB with real data?

Tks guys

I don't understand what you are getting at here. The DatabaseMigrator inspects any tables upon deployment and may drop foreign key contraints so that the table can be updated. In many cases, if this is not done, columns, indexes, etc may not be created due to the contraints.



So in short, I am not sure what your question/issue is. You say that the DBM always reruns a whole command, but I don't really know what you are mean. The DBM does inspect the entire database, as it should. And at times, it may have to drop and recreate indexes and constraints as required by SMO.