ER/Studio - Embarcadero Technologies Product Documentation

USING ER/STUDIO > DEVELOPING THE PHYSICAL MODEL
• Reusable procedures: Created in the data dictionary, reusable procedures can become templated if they are
modified through the Table Editor. You can write templated procedures in BASIC. Reusable procedures are
templated procedures written in BASIC code. These procedures can be applied to any table, since they use the
table’s context in the code. The Reusable Procedure node in the Data Dictionary includes DBMS platform nodes.
ER/Studio organizes reusable procedures by platform. When you want to create, edit, or delete a reusable
procedure, right-click the target DBMS node and then click the appropriate short cut menu.
The following database platforms support Procedures:
• IBM DB2 for LUW 5.x, 6.x, 7.x, 8.x, and 9.x
• Microsoft Access 6.x and 7.x
• Microsoft SQL Server 6.x, 7.x, 2000, 2005, and 2008
• Oracle 7.x, 8.x, 9i, 10g, and 11g
• Sybase ASA 6.0, 7.0, 8.0, 9.0, Adaptive Server IQ 12
• Sybase Adaptive Server IQ 12
• Sybase ASE 11.0, 11.5, 11.9, 12.0, 12.5, and 15
TIP: The Northwind.dm1 sample model illustrates how procedures can be used to gather
information and perform computations on them to provide summary information.
Notes
• You can view the templated procedures associated with a table on the Dependencies tab of the Table Editor.
• You can view the scripted procedures you create under the Procedures tab of the node.
• In order for code to be generated for procedural logic such as triggers and procedures, the results of the code
must be stored in a variable called resultstring. For example, in the Northwind.dm1 sample model, the Data
Dictionary lists a reusable trigger, SYSUPDATE, for the the Oracle platform. The code for this trigger includes the
following statement, which is required for code to be generated for the trigger:
resultstring = trigBody
Create a Scripted Procedure
1 In the Data Model Explorer, expand the physical Main Model, right-click the Procedures node, and then click
New Procedure.
2 Complete the Procedure SQL Editor and then click Validate to ensure the SQL is valid.
3 Click OK to create the procedure and exit the editor.
TIP: Once you have created the auxiliary table, you can edit it by right-clicking the auxiliary table you
want to change, and then selecting Procedure.
The following describe options that require additional explanation.
• In order for code to be generated for procedural logic such as triggers and procedures, the results of the logic
must be stored in a variable called resultstring. For example, in the Northwind.dm1 sample model, the Data
Dictionary lists a reusable trigger, SYSUPDATE, for the the Oracle platform. The code for this trigger includes
the following statement, which is required for code to be generated for the trigger:
resultstring = trigBody
SQL page/tab
Enter the SQL for the procedure.
EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 183