I completely misread your original post. Sorry about that.
As I understand it, you question is how to recognize changes in a
database table so that these changes can become events for the SQLNS
If that's the case, the you can use 3 or 4 part names to reference the
table that will be the source of your events. In your SQL Server Event
Provider, write a query that can be used to identify changes in the
table. You can use views that cover the table to assist. You can also
use Chronicle tables in the SQLNS app to keep track of the records
you've already recognized.
There's another possibility, too. There are some sprocs available in
the SQLNS database that you may be able to call from with a trigger on
your data database to submit event info.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Wed, 25 Jan 2006 00:52:03 -0800, "Franz"
<[email protected]> wrote:
>I'm bound to SQLServer 2000 as a requirement of my customer - not possible
>to switch to SQLServer 2005.
>Are there any tools for SQLServer 2000 I haven't found yet to do the
>"Joe Webb" wrote:
>> If you're using 2005, it sounds like sqldependency may be a better
>> solution for you. Have you check into that?
>> Joe Webb
>> SQL Server MVP
>> Get up to speed quickly with SQLNS
>> I support PASS, the Professional Association for SQL Server.