2. It appears the DDT can't create Logins at the database server level or Users at the database level or am I missing something. It appears the only security it handles is for Microfour's Role-based Security tool.
1. When I imported my schema into a DDT project, one of the tables ended up with 2 primary keys. This table had a primary key defined as an auto-increment field (ID) and a unique index that was a combination of multiple fields. When I deployed to the server an error was displayed when trying to create the primary key (ID) saying the primary key already existed. I checked the DDT project and sure enough both the PK and the unique index were marked as a primary key. The DDT doesn't allow changing of the index type so I had to delete the unique index that the DDT thought was a primary key and readd it as a unique index. Any idea why that would happen? I have several other tables with the same scenario but they imported ok.
2. I created a database installer based on the supplied sample. Everything seems to work fine except, when you click on the Select SQL Server dropdown it does not display the "Searching..." window and the dropdown does not get filled with a list of available servers. I key in the server name and everything works fine but why won't the dropdown get populated?
3. I imported a schema into a DDT project but I want to deploy it to a different database on the same server. I'm assuming all I need to do is change the "Database Name on Server" when the Database Target Names dialog is displayed. I know it will create the database with the right name but will all the underlying files (e.g. .mdf, .log, etc.) get created with the new database name?
Thanks!!