| Groups | Blog | Home |
sql server notification services : Queries
I am working on a project where =20 SQL Server Notifications as a major part of my exploration.=20 There are some practical difficulties I am facing in business = implementation. I would want to discuss with you. I would be really = thankful if you could help me with this.=20 =20 I have NS implemented.=20 It is presently configured to receive single set of events. The events = do not have any condition. Say when I am implementing my subscription = rule. I have no way to provide any trigger value as on what basis NS is = going to process the events and generate the Notifications.=20 =20 a.. I just want the NS to process each event I pass and I should get a = notification with the same values.=20 =20 The subscriber here is a different application which is going to receive = the notification. I need to develop a custom delivery protocol which = will fill in the needs to the destination subscriber. My problem here, = now say if the subscriber crashed and I have still events coming from = Source. Notifications will be generated and will be posted to = subscriber. Now the subscriber is not in a position to receive the = events.=20 =20 How will I handle this scenario, Is there anyway I can know the = subscriber no longer exists. Or is there a way where I can send him the = events since the time he had crashed.=20 =20 Waiting for your earliest response.=20 =20 Thanks!!! Yogesh Kadalgikar =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Do you mean to say we have to manually disable the subscriber.
But I guess I cant do that as it will be automised process and the subscrber can go off and come online at any time. But the requirement at my side is to process all the events and notifications to all the events are received by the Subscriber. Thanks!!! Waiting for your response [quoted text, click to view] "Joe Webb" <joew@webbtechsolutions.com> wrote in message implementation. I would want to discuss with you. I would be reallynews:a0vud15qbbtea6e47vgliirr1tjvssc86n@4ax.com... > What about MSMQ? > > An alternative may be to have your custom protocol log each successful > delivery to the subscriber app. If you have 6 consecutive failures, > disable the subscriber. With this implementation, you're making an > assumption - which is always a little dangerous. > > -- > 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 Thu, 21 Jul 2005 15:15:14 +0530, "Yogesh K." > <yogesh.kadalgikar@rakya.com> wrote: > > >Hi > > > > > > > >I am working on a project where > > > >SQL Server Notifications as a major part of my exploration. > > > >There are some practical difficulties I am facing in business thankful if you could help me with this. [quoted text, click to view] > > not have any condition. Say when I am implementing my subscription rule. I> > > > > >I have NS implemented. > > > >It is presently configured to receive single set of events. The events do have no way to provide any trigger value as on what basis NS is going to process the events and generate the Notifications. [quoted text, click to view] > > the notification. I need to develop a custom delivery protocol which will> > > > > > a.. I just want the NS to process each event I pass and I should get a notification with the same values. > > > > > >The subscriber here is a different application which is going to receive fill in the needs to the destination subscriber. My problem here, now say if the subscriber crashed and I have still events coming from Source. Notifications will be generated and will be posted to subscriber. Now the subscriber is not in a position to receive the events. [quoted text, click to view] > > subscriber no longer exists. Or is there a way where I can send him the> > > > > >How will I handle this scenario, Is there anyway I can know the events since the time he had crashed. [quoted text, click to view] > > > > > > > >Waiting for your earliest response. > > > > > > > >Thanks!!! > > > >Yogesh Kadalgikar > > > >============== > > > > >
What about MSMQ?
An alternative may be to have your custom protocol log each successful delivery to the subscriber app. If you have 6 consecutive failures, disable the subscriber. With this implementation, you're making an assumption - which is always a little dangerous. -- 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 Thu, 21 Jul 2005 15:15:14 +0530, "Yogesh K." [quoted text, click to view] <yogesh.kadalgikar@rakya.com> wrote:
>Hi > > > >I am working on a project where > >SQL Server Notifications as a major part of my exploration. > >There are some practical difficulties I am facing in business implementation. I would want to discuss with you. I would be really thankful if you could help me with this. > > > >I have NS implemented. > >It is presently configured to receive single set of events. The events do not have any condition. Say when I am implementing my subscription rule. I have no way to provide any trigger value as on what basis NS is going to process the events and generate the Notifications. > > > > a.. I just want the NS to process each event I pass and I should get a notification with the same values. > > >The subscriber here is a different application which is going to receive the notification. I need to develop a custom delivery protocol which will fill in the needs to the destination subscriber. My problem here, now say if the subscriber crashed and I have still events coming from Source. Notifications will be generated and will be posted to subscriber. Now the subscriber is not in a position to receive the events. > > > >How will I handle this scenario, Is there anyway I can know the subscriber no longer exists. Or is there a way where I can send him the events since the time he had crashed. > > > >Waiting for your earliest response. > > > >Thanks!!! > >Yogesh Kadalgikar > >============== > >
Check out MSMQ. I think that may be what you're looking for.
-- 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 Thu, 21 Jul 2005 16:35:39 +0530, "Yogesh K." [quoted text, click to view] <yogesh.kadalgikar@rakya.com> wrote:
>Do you mean to say we have to manually disable the subscriber. > >But I guess I cant do that as it will be automised process and the subscrber >can go off and come online at any time. > >But the requirement at my side is to process all the events and >notifications to all the events are received by the Subscriber. > >Thanks!!! > >Waiting for your response > >"Joe Webb" <joew@webbtechsolutions.com> wrote in message >news:a0vud15qbbtea6e47vgliirr1tjvssc86n@4ax.com... >> What about MSMQ? >> >> An alternative may be to have your custom protocol log each successful >> delivery to the subscriber app. If you have 6 consecutive failures, >> disable the subscriber. With this implementation, you're making an >> assumption - which is always a little dangerous. >> >> -- >> 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 Thu, 21 Jul 2005 15:15:14 +0530, "Yogesh K." >> <yogesh.kadalgikar@rakya.com> wrote: >> >> >Hi >> > >> > >> > >> >I am working on a project where >> > >> >SQL Server Notifications as a major part of my exploration. >> > >> >There are some practical difficulties I am facing in business >implementation. I would want to discuss with you. I would be really >thankful if you could help me with this. >> > >> > >> > >> >I have NS implemented. >> > >> >It is presently configured to receive single set of events. The events do >not have any condition. Say when I am implementing my subscription rule. I >have no way to provide any trigger value as on what basis NS is going to >process the events and generate the Notifications. >> > >> > >> > >> > a.. I just want the NS to process each event I pass and I should get a >notification with the same values. >> > >> > >> >The subscriber here is a different application which is going to receive >the notification. I need to develop a custom delivery protocol which will >fill in the needs to the destination subscriber. My problem here, now say if >the subscriber crashed and I have still events coming from Source. >Notifications will be generated and will be posted to subscriber. Now the >subscriber is not in a position to receive the events. >> > >> > >> > >> >How will I handle this scenario, Is there anyway I can know the >subscriber no longer exists. Or is there a way where I can send him the >events since the time he had crashed. >> > >> > >> > >> >Waiting for your earliest response. >> > >> > >> > >> >Thanks!!! >> > >> >Yogesh Kadalgikar >> > >> >============== >> > >> > >> >
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 |