Hi Steve -
The scenario you described sounds like a very good implementation for
SQLNS. As I'm sure you noticed in your research, SQLNS is a framework
for rapidly building and hosting highly scalable notification
applications. Even if you don't necessarily need the scalability
aspect, you can still benefit from the development framework and what
it has to offer (scheduling, retries, event providers, etc).
Having said that, you may also want to check out Query Notifications
in ADO.NET 2.0. If you can wait until Nov 7th, it may even be a better
solution for you.
SQL Server MVP
Get up to speed quickly with SQLNS
I support PASS, the Professional Association for SQL Server.
On Wed, 29 Jun 2005 11:20:16 -0700, "Steve" <[email protected]> wrote:
>We will have about 10 clients apps connecting to our data store. When one
>client changes a record or in any way modifies the data store I would like
>to have the other clients get that data.
>So I can either have the clients poll the data store asking for changes or I
>thought this might be a good use of notification services. I downloaded the
>PPT file about notification services and it gave me the impression that it
>was designed for much larger scale applications, that to use it for my needs
>might be overkill.
>To take it one step further, I would like to push the new data to the client
>only if their current query matches the data that has been modified, for
>this, again.. notification services seem to be appropriate.
>If you have any suggestions either way, I would appreciate them.