I'm a little stumped by this one ... just about every time I deploy from the DDT to the development database I usually get a message stating that the SP already exists in the server.  Well, yes, in fact it does ... I'd kind of like you to overwrite it if it is different.

The odd thing is that this does not happen with every stored procedure that already does exist.  The DDT just goes on its merry way either overwriting or ignoring (don't know which) the exiting stored procedure.

Why do some SPs generate this warning and some don't?

In order to get a clean deployment I have to delete those stored procedures the DDT does not like and run the deployment again.

Stumped.

Thanks.

Charles T. Blankenship
Senior Consultant
Novant Consulting, Inc.
704.975.7152
http://www.novantconsulting.com