I have been playing with the DDT with auto-generating stored procedures and have manged to somehow have two empty auto-generated stored procedures (see attached image).



So now I naturally get errors when deploying to server but I cannot seem to get rid of the empty stored procedures. The error I get when deploying indicates that these procedures belong to my Customers table and I ended up turning off the auto-generate in all of my table properties then generate the package and there the empty things are, smiling at me (actually they're probably at the giggling stage now ).



Am I missing something obvious, I have tried everything I can change, click or edit in the DDT but to no avail. Any help would be greatly appreciated.



Cheers,

Keith.

Well it's good to hear we got past problem A, problem B is a bit of an odd one, isn't it?

Can you copy and paste the Sproc code that actually got deployed to your server. You can get to it through SQL Management Studio (they will be under the Programmability folder of your deployed database.) I'd like to see if something weird got put into the autogenerated code.

There is no ExerciseParts_Delete sproc code deployed to the server. I tried changing the concurrency option, removing then adding adding the sproc under a different name but it never gets deployed.



As the ExerciseParts table is only a small table I deleted it, removed it from the history then recreated it from scratch and bingo it now deploys fine. As the DDT is used by a large number of people all over the place I doubt the problem is from there. I am assuming that when I imported this table from the previous database it carried something in with it that deleting and recreating from scratch cleared up.



Thanks for the help and enjoy your weekend, its about 50 degrees fahrenheit and raining here so is only good for staying inside.



Cheers, Keith