So, one more question. If I don't define any views or sprocs in DDT, will it still delete all existing views/sprocs in the database?

They get deleted and recreated every time. 

Just be absolutely clear (as this is NOT something I want to make a mistake on), I have a profile with NO sprocs or views defined (I would have tables defined though) and I deploy this package to an existing database that has existing views/sprocs, after the deployment, I would have no views or sprocs in the database, right?

Correct.

OK, so if I just wanted to use the DDT to deploy data (never schema) how would I do that?

Look at the Database Installer Sample that is in the Samples and Solutions section of the forum.  This sample shows you how to use the DatabaseMigrator class.  The meta-data and data deployment are two different methods.

Glad to here it. I'll look at the sample again (this time I'll try to absorb more of it). I don't think the DDT will work at all for my normal db updates, but I'm using for my security db (separate db, no fancy-smancy SQL stuff to work about) and it works great and I'm hoping I can use it to update some static application data. That will be nice



Thanks for all the info!

Sorry for thread-hijack

Are you sure about that ? Because when i put comments into the pre-create/environent code block within the ddt, it doesnt show on the sql server after deployment.

Hah, quite the hi-jack, there .

It used to keep those comments, but the way in which the DDT handles stored procedures has changed quite a bit in the last year an a half. The editing and maintenance tools are now a lot more robust, but it will also clean out any comments (as you discovered) from the pre-create/environment code block.

Any comments used within the main code block, however, will be left untouched at deployment time.