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

Trent,

DDT is almost perfect, before it I tested and used this solution:

http://www.xsqlsoftware.com/Product/Sql_Schema_Compare.aspx

DDT is so different than other solutions, but I thought basically in a save snapshot concept, for example:

- Day 23 I include a field, the DDT knows the version of DB a proccess only ALTER TABLE ADD XYZ.

http://www.xsqlsoftware.com/Product/xSQL_Database_Version_Control.aspx

My main problem is the time consumption for DDT deploying in a same server, I have 100 tables and DBM spend 3 minutes per database.

Ok... It´s !!!!

See ya....

Thanks for your input Luiz.  The DDT is a very complex tool and does a lot.  Providing the ability to avoid scripts as well as move from version 1 to 10 in a single step requires some testing and configurations.  However, I do receive your input and one of the things high on our list is a new version of the DDT.  I agree that there are times when speed is an absolute.  I am not sure why it is taking 3 minutes as our medical app has over 200 tables, hundreds of sprocs, dozens of views, CLR assemblies, and plenty of UDFs and it doesn't take 3 minutes (unless running in a porr environment which can happen from time to time).  All of that being said, there is always room for improvement and learning from current versions...that is why there is always a next version!   Thanks for your business and input.