We recommend that you divide your application into functional areas, and then create one SAM for each functional area.

For example, if you are building a customer services application, you might create separate SAMs in DB/Assist for inventory, accounts payable, accounts receivable, and customer information.

Within each SAM, you should group SQL statements by function so that developers can work on different pieces of the application simultaneously. To avoid creating duplicate SQL statements, we recommend that you group common SQL statements for general use throughout the application.

We do not have a recommendation for the number of SAMs you should use in your application. However, we do recommend including many SQL statements in each SAM.

Keep in mind that each SAM results in a bind file. At run time, you or your network administrator will need to manually bind each bind file to the database.