Use Dynamic SQL Statements

If you select the Use Dynamic SQL Statement option, a custom data access class is not generated for your business object. Instead, a generic data access class (such as mmDataAccessSql or mmDataAccessOracle) is used at run time in conjunction with your business object for accessing and manipulating data:

At run time when a business object requests that the data access object update data, Insert, Update, and Delete SQL commands are dynamically generated to perform these tasks.

When using Entity Framework, this task is performed by the Entity Framework. When using classic MM .NET entity objects, this job is handled by the ADO.NET CommandBuilder object.

In either case, this is efficient when updating existing data, since only the columns that have been changed are sent to the database as part of the SQL UPDATE command. This is important if you have many triggers on your database--you don't want them firing unnecessarily as they would be if all columns were indiscriminately updated.

See Also:

Step 5: Generate Business Layer Classes | Create New Stored Procedures | Use Existing Stored Procedures