> I started out to use the .NET SqlDependency mechanism, based on
> QueryNotificationService if I have the vocab correct, and have run into
> a limitation that seems like it will prevent this from working out for
> me, at least in the way I had hoped and planned...
>
> Specifically, when adding a SqlDependency to a stored procedure, a
> subscription is (attempted) to be created on each statement inside the
> stored procedure. Even if the statement doesn't return any rows outside of
> the stored procedure, including internal selects and sets:
>
> select a, b, c from dbo.mytable -- fine
> select @err = @@error -- causes subscription error
>
> Effectively, this appears to mean that one can't use query notifications
> on anything but the most trivial of stored procedures (a single select
> statement)
>
> Seems to me that the only useful behavior would be to track the actual
> result(s) of the query - return parameters and actual result sets returned
> to the caller. Tracking each internal statement can't be good for anybody.
>
> Is there some good reason for this, or have I completely missed something?