1. I import the DB in the DDT. I call this DB version 1 and I deploy it to customers.

2. I make changes to the DB, but not using the DDT. Mostly with scripts, and the SQL Server Management Studio. This is version 2 of the DB. I import the DB to the DDT again. By deploying this new package, will the DB modified correctly?

Can I use this method of just importing the DB to the DDT with every new version of the DB I wish to deploy? Will it work? I need this because changes might happen to the DB schema by more than one people, not everyone has the DDT installed and most of those people got used to modifying the schema using SQL Managment Studio or MS Access (for SQL 2000).

Thank you for your time.

This is the entire purpose of the DDT.  To deploy to a server (new or existing database) and have those structures updated without running scripts or having to deploy in a sequential order (in the event that there have been other releases between the current version and installing version).

Maybe....the reason is because this is not how the DDT was designed to work.  The DDT was designed to import a database, but from that point forward the meta-data should be maintained within the DDT itself.  There is a bit of logic that keeps up with the changes that occur so that an accurate depiction of what needs to be changed is logged.  If you continue to make changes through SQL Management Studio and expect all of the meta-data logic to figure everything out, especially relating to data-type or field name changes, then you will have an issue.