I also don't know exactly what you are trying to do. You can not have a "trigger" on a stored procedure. Your updates and inserts are part of the stored procedure. If you want a total for your view, you can write a function to return your count. This function can be incorporated into a view, if need be. Is is also possible to update and insert via a view. If a simple view (no joins), an insert/update can pass through it. If a complex view, then an "Instead Of Trigger" can be used. When an insert/update is applied to the complex view, this trigger takes over processing. A bit of advice, trigger should not have very much code associated with it. If a trigger start getting overly large, then call a stored procedure from the trigger.