> With "debugging", I also meant such goodies like breakpoints,
> step-by-step execution, watches and so on.

To find out where your trigger wanders and what's in variables
you can use UDF which shows dialog box (on the server, of course).

Sometimes you may just want to know whether/how many times
the processing passed over specific point - then just put gen_id()
in that place.

When debugging SP you can also put SUSPEND at appropriate
places and return debug informations via output parameters.

Ivan