I am just using a trigger to INSERT INTO the view created for the
EventClassName created by NS.
I am adding logic to the INSERT statement for the Chronicle to not insert a
record if there is one already there for the same data. It is working for
"Joe Webb" <[email protected]> wrote in message
> Are you using an event provider to submit records to your Chron table?
> If so, that's where the dups are likely coming from. The Chron table
> should be populated by the Chron rule, not the event provider.
> Joe Webb
> SQL Server MVP
> Get up to speed quickly with SQLNS
> I support PASS, the Professional Association for SQL Server.
> On Tue, 6 Sep 2005 13:20:57 -0400, "Andy" <[email protected]>
>>INSERT INTO LoadAddedLog(
>> FROM LoadAdded e
>>This is defined in the
>>"kate" <[email protected]> wrote in message
>>> what does your chronicle insert rule look like?
>>> it can also be really useful to add a datestamp to the chronicle
>>> records to you can see when they arrived.
>>> Kate MBCS
>>> Alert Technologies
>>> Get your notification services implementation going in minutes not
>>> weeks ......