microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

Re: Chronicle Debugging

Subject: Re: Chronicle Debugging
From: Joe Webb
Date: Wed, 07 Sep 2005 14:50:51 -0500
Newsgroups: microsoft.public.sqlserver.notificationsvcs
As you've already discovered, that's not a recommended approach. Check
BOL for these stored procedures. They can be used to submit events
from triggers.

NSEventBeginBatch<EventClassName> 
NSEventSubmitBatch<EventClassName> 
NSEventFlushBatch<EventClassName>
NSEventWrite<EventClassName> 



HTH...


-- 
Joe Webb
SQL Server MVP


~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)


On Wed, 7 Sep 2005 12:49:12 -0400, "Andy" <[email protected]>
wrote:

>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 
>me.
>
>
>"Joe Webb" <[email protected]> wrote in message 
>news:[email protected]
>> 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.
>>
>> HTH...
>>
>> -- 
>> Joe Webb
>> SQL Server MVP
>>
>>
>> ~~~
>> Get up to speed quickly with SQLNS
>> http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
>>
>> I support PASS, the Professional Association for SQL Server.
>> (www.sqlpass.org)
>>
>>
>> On Tue, 6 Sep 2005 13:20:57 -0400, "Andy" <[email protected]>
>> wrote:
>>
>>><ChronicleRule>
>>><RuleName>UpdateLoadAddedLog</RuleName>
>>><Action>
>>>INSERT INTO LoadAddedLog(
>>>      LoadNumber,
>>>      Terminal,
>>>      ContactPhone,
>>>      PickupDate,
>>>      OriginCity,
>>>      OriginState,
>>>      OriginLat,
>>>      OriginLong,
>>>      DestinationCity,
>>>      DestinationState,
>>>      DestinationLat,
>>>      DestinationLong,
>>>      TrailerGroup,
>>>      TrailerType,
>>>      LoadType,
>>>      Revenue,
>>>      RatePerMile,
>>>      Miles,
>>>      Preloaded,
>>>      TeamLoads,
>>>      TimeAdded
>>>      )
>>>      SELECT
>>>      e.LoadNumber,
>>>      e.Terminal,
>>>      e.ContactPhone,
>>>      e.PickupDate,
>>>      e.OriginCity,
>>>      e.OriginState,
>>>      e.OriginLat,
>>>      e.OriginLong,
>>>      e.DestinationCity,
>>>      e.DestinationState,
>>>      e.DestinationLat,
>>>      e.DestinationLong,
>>>      e.TrailerGroup,
>>>      e.TrailerType,
>>>      e.LoadType,
>>>      e.Revenue,
>>>      e.RatePerMile,
>>>      e.Miles,
>>>      e.Preloaded,
>>>      e.TeamLoads,
>>>      getutcdate()
>>>      FROM LoadAdded e
>>></Action>
>>></ChronicleRule>
>>>
>>>This is defined in the
>>>"kate" <[email protected]> wrote in message
>>>news:[email protected]
>>>> 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
>>>> http://www.alert-technologies.co.uk
>>>> Get your notification services implementation going in minutes not
>>>> weeks ......
>>>>
>>> 
>

<Prev in Thread] Current Thread [Next in Thread>