> One of the problems we are running into, is that some people like
> to use one tool for
> everything. Currently Stored Procedures and Triggers use a
> variation of SQL to do
> their job. Changing this to use Java or Pascal or Basic even,
> isn't going to make
> the process easier, in some ways it simply makes the engine more
> complex and
> larger, without adding any real functionality.

IMHO.. ANSI has a standard for SQL but not for procedures and triggers
(atleast not that I am aware of). This makes the job of moving code
("business logic") from one RDBMS to another all the more complex and
major corporations like Oracle,MS,IBM and Sybase don't want that
because customers have the freedom to go elsewhere...

>
> An easier way of doing the same thing, is to determine what
> constructs are missing
> from the existing SP/Trigger language, and to extend it, to add
> those capabilities.
>

There should really be a common SP/Trigger language (ANSI standard)
that is geared to allow data manipulation efficiently and effectively.

Nirmal