I agree with Kate - there is probably a more direct method to
accomplish your goals.
However, if that's the route you want to take, the matching rule is
really just a T-SQL statement. Version 2.0 uses a UDF to create the
resultset while v2005 uses a new view to do the same.
BTW - matching rules are processed in the following order:
- Event chronicle rules
- Subscription event rules
- Subscription scheduled rules
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On 9 Nov 2005 15:02:23 -0800, "kate" <[email protected]> wrote:
>It seems a bit odd to be storing multiple events when you dont want to
>use them. Is there some other reason why you are storing duplicate
>events that you dont want? It would be better to put the duplicates
>into the chronicle and put the uniques into the events table.
>That said, if you want to strip out the duplicates then you need to
>define the generator rule such that only the unique events are
>extracted, how to do this depends on if your data has any natural keys.
>what does your generator rule look like?
>Are you using sql2000 or 2005 ?
>Get your notification services implementation going in minutes not