Hi Vadim -
Congrats on getting your first SQLNS app going! Welcome to the group!
I'd suggest going through the walk-through provided in BOL. It'll
provide some good insight into how SQLNS works, the basic principles,
There are a couple of other good resources, too. Shyam Pather has an
excellent book on the subject, 600+ pages of detailed informatoin.
I've also got a book out there that's designed to help people get up
to speed with SQLNS very quickly.
I've also got some demo's and samples available on the downloads page
of my web site - http://www.webbtechsolutions.com/downloads.aspx.
The short answer to your question is that you're going to want to
configure your event provider to recognize only new events. Change the
T-SQL to identify only the new rows. You can compare this to
information you've stored in a Chron table or you can update the
original table after you've queried it, marking the identified rows as
having been entered into the system. Either way will work.
Chron tables have other uses too, including preventing reduntant
notifications, etc. Check out the subject in BOL.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Fri, 21 Jul 2006 22:35:51 -0500, "Vadim Rapp"
<[email protected]> wrote:
>after some struggle, I created my first trivial notification applicaiton.
>One problem I don't quite understand. Let's say, I want to generate
>notification whenever in the table1 there's new record with col1='x'. Will
>NS ensure that each such record generates only one notification, or it's
>something I have to do? if the latter, how?
>So far, I based my trivial application on SELECT ID FROM TABLE1 WHERE
>COL1='X' ; and NS generates the same notifications about each such row in
>every cycle, over and over again.