>Hi,
>
>Is there a command to stop Stored proceedures from firing, other than setting a maintenance mode switch in each of the SP's.

I don't think so. A stored procedure is just like any other function, except for the place where it is stored; if you invoke it, it runs.

However, for the special case of referential integrity procedures, if you use some alternative referential integrity system such as TaxRI, the control variables (to let you skip the function) may already be established.

For example: For updating the database, I do an APPEND FROM for each table. This may make the referential integrity triggers fire again, making the update slow, and provoking errors if I happen to copy the child table before the parent table.

In this case, disabling RI (through the variables provided by TaxRI) will solve both of these problems.

Also, when I update a table of purchases, a trigger will fire to update the inventory. Here, updating the inventory once again would not only be slow, it would be plainly wrong. In this case, I re-use the same variable defined by TaxRI, to conditionally abort the update function, and thus avoid the extra update.

HTH,

Hilmar.