If you use the DDT most of the work will be done for you. The BO side of things will not change much regardless of whether you create the sprocs manually or use the DDT. So let's start there. If you use the DDT all you need to do is indicate that you want thte DDT to automatically create the INSERT, UPDATE, and/or DELETE stored procedures for you.
The above image shows that this table is having the DDT automatically create the INSERT and UPDATE stored procedures for it. This will generate and deploy all of the T-SQL stored procedure code for you....no T-SQL knowledge required! Very cool!!!
If you leave the default naming convention intact as you seen above (TableName_Action) then all you need to do is indicate that you want to use the sprocs on the BO and you do not even have to provide the sproc name.
If you go the manual route of creating the sprocs, refer to the docs in the help topic: Database Deployment Toolkit -> Stored Procedures -> Table CRUD Stored Procedures. This will give you a T-SQL example of each of the sprocs. This is obviously going to be a bit more work and complicated since you will be manually creating the stored procedures. However, the BO is really no more work. Just as above, you will indicate that you want to use the sproc. Then be sure to provide the stored procedure name if it does not follow the default naming convention.
