SQL Trigger + CLR SP vs CLR Trigger
Are there any benefits to call CLR SQL stored procedure from regular trigger rather then deploy CLR trigger straight away? I need to be notified on specific column change (StatusID) in very large table. Currently a number of windows services is used. Each monitors its own StatusID, i.e. quires db for specific StatusID: SELECT a,b,c FRO...