Alternatively, are you saying that there are certain cases where your code should be able to update a table without invoking that table's trigger?
If so, the following method is inelegant but works...
1. Add a bit column called "SupressTrg" (for instance) to the table involved.
2. When your code updates the table, make sure the update also sets a value for "SupressTrg" (true or false depending on whether or not the trigger should be supressed).
3. Structure your trigger along these lines
CREATE TRIGGER trgMyTrigger ON tblMyTable
FOR UPDATE
AS
-- Is trigger supressed?
IF EXISTS (SELECT SuppressTrig
FROM inserted
WHERE (SuppressTrig = 0))
BEGIN
-- Nope, so execute trigger code
-- (trigger code here)
END
-- Reset trigger supression flag
UPDATE tblMyTable
SET SupressTrig = 0
FROM tblMyTable, inserted
WHERE tblMyTable.PK = inserted.PK
Horrible, I know, but I have used this method successfully to get myself out of a corner I'd managed to paint myself into.