Here's a thread that may help with passing optional parameters.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On 3 Mar 2006 03:58:42 -0800, "gotcha" <[email protected]> wrote:
>I also came up with that idea.
>There are some events which I should be able to merge into one event
>class, with an extra parameter.
>This would work quite well for events like "document added" and
>"document changed", because their event classes are almost the same,
>and users subscribe to these events in the same way.
>However, some other document-related events are less suitable for
>These events have other event fields and other subscription parameters.
>For example, users can receive a notification when the end of the
>publication term for a document approaches.
>In their subscription, they're able to set the number of days before
>the end date they want to be warned.
>Merging all event classes would be possible, but it would leave me with
>complicated event classes and lots of subscription parameters.
>In addition to that, users should still be able to subscribe to some of
>the merged events, and not all.
>This would result in another subscription parameter, which should hold
>all the events the user subscribed to.
>If there is no better solution, I'll try to work something out with
>merged event classes, but I was hoping there was a better