One small clarification: Joes is correct, but even in v2.0, you can call
stored procedures in your match rules to determine what has matched etc. You
just have to make sure that you ultimately call the Notify() function to get
the notifications into the notifications table.
-shyam
--
Learn more about SQL-NS:
http://www.amazon.com/exec/obidos/tg/detail/-/0672326647/ ---------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm. ---------------------------------------------
[quoted text, click to view] "Joe Webb" <joew@webbtechsolutions.com> wrote in message
news:uVtCs0gLFHA.1528@TK2MSFTNGP09.phx.gbl...
> Hi Jplankala -
>
> In v2.0, the EventRule and ScheduledRule must use the notification
> function provided.
>
> In SQL Server 2005, T-SQL and Stored Procedures may be called in the
> Action element of the EventRule and ScheduledRule nodes.
>
> HTH...
> Joe Webb
> SQL Server MVP
>
> ~~~
> Get up to speed quickly with SQLNS
>
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 >
>
>
>
> jplankala wrote:
> > Most of my business knowledge for generating Notification conditions are
> > currently residing on .NET components and SQL stored procedures. I would
like
> > to reuse it for the SQL notification services.
> >
> > is there any way to incorporate the Stored procedure calls or .NET
component
> > calls in the Action part of ScheduleRule or event rule?
> >
> > Please advice me.
> >
> > Jplankala.
