Foxhound is the better* Database Monitor for SQL Anywhere.
*better: More thorough, more relevant, more effective.
...more Alerts, more All Clears, more details, more control in your hands.
|
[Home] | [Table of Contents] | [Previous Section] | [Next Section] |
Breck Carter
Last modified: February 12, 1998
mail to: bcarter@bcarter.com
Database-intensive application logic will sometimes run faster if it is contained within a SQL Anywhere stored procedure or trigger. One reason might be that SQL Anywhere's procedure language simply runs faster than the application programming language in use. Another reason is that less application-to-database communication is required when repeated SQL operations are embedded within a procedure that is only called once. A third reason is that once a procedure or trigger has been loaded and compiled it is kept in virtual memory and can be used concurrently by several applications or recursively by one application.
Figure 32A shows a PowerBuilder script that updates 1000 rows via PowerScript embedded UPDATE statements. Figure 32B shows a PowerBuilder script that accomplishes the same thing in one quarter the time by calling the stored procedure in Figure 32C.
Figure 32A - Slow PowerBuilder UPDATE Loop
|
Figure 32B - Fast PowerBuilder Procedure Call
|
Figure 32C - The UPDATE Loop In A Stored Procedure
|
[Home] | [Table of Contents] | [Previous Section] | [Next Section] |