Hi there guys.

The whole thing started when I tried to modify a foreign key constraint. Then when trying to deploy the package I got an exception saying that a certain field (which is the primary key) could not be renamed because it was a member of a list. I have removed the constraint and add it again, and the same error.

After that I have removed the whole table and recreated it. Not I get four exceptions: One that says that a certain view (which depends on the table) could not be created because the table is not there. I have remove and recreated the view too, but still the same error.

The other two exceptions complain that they cannot verify the existence of the indexes in the table and view which I have removed and recreated.

The fourth complains about not being able to verify the existence of foreign keys in the table that has been removed and recreated.

Is there a chance that I'm doing something terribly wrong with DDT? I have imported the tables from a SQL2005 database and created all indexes and stored procedures and views manually in the DDT. After that all I do is modifying the schema. Is there a certain way I must be using the DDT tool? Is this because DDT is a rather new tool?

I have attached a rar file that contains my database, my StrataFrame database, the package, and the result log files of the deployments, in case you'll need to look more into it.

Thank you in advance.

George,



I'd highly recommend what Trent is saying. I've had a number of problems, in various arenas, and when stuff like this starts happening (just weird stuff, that after 3 or 4 times looking into it, is just getting weirder) its time to start limiting what could be wrong. In this case, its using the package to deploy to a brand new database, with nothing in it. If it works, then it isn't the package. You can compare the two databases (the one driving you crazy and the new one) to see what's different. When I'm coding in VS and problems like this start happening, first I usually post here. There have been times when my weird problem is actually a known issue and there is a way to deal with it. If it isn't and if it starts getting weird on me, I often start a new project, and try to isolate the problem, or do a fresh check out from source control or try another machine. I try to do this before I start banging my head on the desk...though if you peruse the forums you will see a few times when I received the same advice and much head banging had already happened. Limiting the problem has helped every time. Good luck!