|
|
You're in the
sql server notification services
group:are notification services correct for my needs?
sql server notification services:
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. Thank you, Steve
Hi Joe, thanks for the response!
Query Notifications sounds PERFECT, very exciting stuff. I will wait for ado.net 2.0. There might even be a beta that I could get involved with to start the development. Thanks again! Steve [quoted text, click to view] "Joe Webb" <joew@webbtechsolutions.com> wrote in message news:frr5c1hnepm4amhdp09pn8fbbicet2buh4@4ax.com... > 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. > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/querynotification.asp > > > 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, 29 Jun 2005 11:20:16 -0700, "Steve" <sss@sss.com> 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. > > > >Thank you, > >Steve > > >
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. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/querynotification.asp 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) [quoted text, click to view] On Wed, 29 Jun 2005 11:20:16 -0700, "Steve" <sss@sss.com> 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. > >Thank you, >Steve >
http://msdn.microsoft.com/getthebetas/
-- 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) [quoted text, click to view] On Wed, 29 Jun 2005 13:03:19 -0700, "Steve" <sss@sss.com> wrote:
>Hi Joe, thanks for the response! > >Query Notifications sounds PERFECT, very exciting stuff. I will wait for >ado.net 2.0. There might even be a beta that I could get involved with to >start the development. > >Thanks again! >Steve > > >"Joe Webb" <joew@webbtechsolutions.com> wrote in message >news:frr5c1hnepm4amhdp09pn8fbbicet2buh4@4ax.com... >> 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. >> >> >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/querynotification.asp >> >> >> 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, 29 Jun 2005 11:20:16 -0700, "Steve" <sss@sss.com> 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. >> > >> >Thank you, >> >Steve >> > >> >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |