|
|
You're in the
sql server notification services
group:Application Relationship Map
sql server notification services:
I think an important part of quickly understanding a new application is
knowing how the various entities in the application relate to one another. Is there relationship map for NS ? For example, it would show you the relationship between the various parameters in the instance and app config files as well as the relationship between the event, subscribers, subscriptions, chronicles settings, etc. Any thoughts ?
I don't know of any such document for NS.
Though NS can be a bit intimidating at first, if you do the walkthrough in the Books Online and play with some of the samples, you'll be able to see pretty quickly how the pieces fit together. Is there a specific question you have about how to build your application? Thanks -shyam -- Learn more about SQL-NS: http://www.amazon.com/exec/obidos/tg/detail/-/0672326647/ --------------------------------------------- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. --------------------------------------------- [quoted text, click to view] "RDV" <roger.vaught@ipaper.com> wrote in message news:1113268708.211175.148360@z14g2000cwz.googlegroups.com... > I think an important part of quickly understanding a new application is > knowing how the various entities in the application relate to one > another. Is there relationship map for NS ? > > For example, it would show you the relationship between the various > parameters in the instance and app config files as well as the > relationship between the event, subscribers, subscriptions, chronicles > settings, etc. > > Any thoughts ? >
Roger -
I gave a presentaion on SQLNS in Orlando last year at PASS (sqlpass.org). In it, I talked about how all the different components relate to each other. Though not really a map, maybe it'd help a bit. You can download the ppt file from the downloads section of my site (http://www.webbtechsolutions.com) if you'd like. As Shyam said, go through the Stocks walkthrough; it'll help put the pieces together for you. HTH... Joe Webb SQL Server MVP ~~~ Get up to speed quickly with SQLNS http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 [quoted text, click to view] Shyam Pather [MSFT] wrote:
> I don't know of any such document for NS. > > Though NS can be a bit intimidating at first, if you do the walkthrough in > the Books Online and play with some of the samples, you'll be able to see > pretty quickly how the pieces fit together. > > Is there a specific question you have about how to build your application? > Thanks
The examples tend to trigger off of absolute conditions. For example,
let me know when a stock price is > a value. Can you create a subscription rule where the operator is included in the subscription? For example, a single subscription template would allow you to determine when the stock is <, >, = to a value. The user would choose the operator when setting up the subscription. What would this look like?
RDV -
The current version of SQLNS doesn't really provide a *direct* way for you to allow users to select the operator for the subscription. But there are a couple of ways to do it leveraging the flexibility of the current architecture. First you can, of course, create multiple subscription classes, one for each possibility. In your stock example, there'd be three - >, <, and =. This is straightforward to do so I won't expound on this option. But, there is a way to do it with just one subscription class. You can create the subscription class with multiple conditions, allowing the user to specify only the ones that apply to them. For example, let's say the event data has StockSymbol and StockPrice as it's fields. A subscription class could be created that has StockSymbol, PriceGreaterThan, PriceLessThan, and PriceEqualTo. (I'm using your example, but realistically the PriceEqualTo wouldn't be very useful.) Your matching rule needs to make some of these conditions optional by including some OR's in the WHERE clause. Something like this: SELECT StockNotify(<parameter list goes here>) FROM StockEvents e, StockSubscriptions s WHERE e.StockSymbol = s.StockSymbol AND ((s.PriceGreaterThan IS NULL) OR (e.StockPrice > s.PriceGreaterThan)) AND ((s.PriceLessThan IS NULL) OR (e.StockPrice < s.PriceLessThan)) AND ((s.PriceEqualTo IS NULL) OR (e.StockPrice = s.StockPrice)) Your Subscription Management Application would then be designed to allow users to specify a stock symbol and one or more of the conditions. A stock symbol is required, but the others are not (You should of course require at list one, but that's a front end issue). HTH... Joe Webb SQL Server MVP ~~~ Get up to speed quickly with SQLNS http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 [quoted text, click to view] RDV wrote:
> The examples tend to trigger off of absolute conditions. For example, > let me know when a stock price is > a value. Can you create a > subscription rule where the operator is included in the subscription? > For example, a single subscription template would allow you to > determine when the stock is <, >, = to a value. The user would choose > the operator when setting up the subscription. > What would this look like?
Thanks for the link. These slides look great! Do you mind if I crib from
the liberally for an internal presentation, with attribution? [quoted text, click to view] "Joe Webb" wrote:
> RDV - > > The current version of SQLNS doesn't really provide a *direct* way for > you to allow users to select the operator for the subscription. But > there are a couple of ways to do it leveraging the flexibility of the > current architecture. > > First you can, of course, create multiple subscription classes, one for > each possibility. In your stock example, there'd be three - >, <, and =. > This is straightforward to do so I won't expound on this option. > > But, there is a way to do it with just one subscription class. You can > create the subscription class with multiple conditions, allowing the > user to specify only the ones that apply to them. > > For example, let's say the event data has StockSymbol and StockPrice as > it's fields. A subscription class could be created that has StockSymbol, > PriceGreaterThan, PriceLessThan, and PriceEqualTo. (I'm using your > example, but realistically the PriceEqualTo wouldn't be very useful.) > > Your matching rule needs to make some of these conditions optional by > including some OR's in the WHERE clause. Something like this: > > SELECT StockNotify(<parameter list goes here>) > FROM StockEvents e, StockSubscriptions s > WHERE e.StockSymbol = s.StockSymbol > AND ((s.PriceGreaterThan IS NULL) OR (e.StockPrice > s.PriceGreaterThan)) > AND ((s.PriceLessThan IS NULL) OR (e.StockPrice < s.PriceLessThan)) > AND ((s.PriceEqualTo IS NULL) OR (e.StockPrice = s.StockPrice)) > > Your Subscription Management Application would then be designed to allow > users to specify a stock symbol and one or more of the conditions. A > stock symbol is required, but the others are not (You should of course > require at list one, but that's a front end issue). > > > > HTH... > Joe Webb > SQL Server MVP > > ~~~ > Get up to speed quickly with SQLNS > http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 > > > > RDV wrote: > > The examples tend to trigger off of absolute conditions. For example, > > let me know when a stock price is > a value. Can you create a > > subscription rule where the operator is included in the subscription? > > For example, a single subscription template would allow you to > > determine when the stock is <, >, = to a value. The user would choose > > the operator when setting up the subscription. > > What would this look like? > >
Not at all! (Thanks for asking, though.)
Hope they find the information useful! HTH... Joe Webb SQL Server MVP ~~~ Get up to speed quickly with SQLNS http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 [quoted text, click to view] MarkSW wrote:
> Thanks for the link. These slides look great! Do you mind if I crib from > the liberally for an internal presentation, with attribution? > > "Joe Webb" wrote: > > >>RDV - >> >>The current version of SQLNS doesn't really provide a *direct* way for >>you to allow users to select the operator for the subscription. But >>there are a couple of ways to do it leveraging the flexibility of the >>current architecture. >> >>First you can, of course, create multiple subscription classes, one for >>each possibility. In your stock example, there'd be three - >, <, and =. >>This is straightforward to do so I won't expound on this option. >> >>But, there is a way to do it with just one subscription class. You can >>create the subscription class with multiple conditions, allowing the >>user to specify only the ones that apply to them. >> >>For example, let's say the event data has StockSymbol and StockPrice as >>it's fields. A subscription class could be created that has StockSymbol, >>PriceGreaterThan, PriceLessThan, and PriceEqualTo. (I'm using your >>example, but realistically the PriceEqualTo wouldn't be very useful.) >> >>Your matching rule needs to make some of these conditions optional by >>including some OR's in the WHERE clause. Something like this: >> >>SELECT StockNotify(<parameter list goes here>) >>FROM StockEvents e, StockSubscriptions s >>WHERE e.StockSymbol = s.StockSymbol >>AND ((s.PriceGreaterThan IS NULL) OR (e.StockPrice > s.PriceGreaterThan)) >>AND ((s.PriceLessThan IS NULL) OR (e.StockPrice < s.PriceLessThan)) >>AND ((s.PriceEqualTo IS NULL) OR (e.StockPrice = s.StockPrice)) >> >>Your Subscription Management Application would then be designed to allow >>users to specify a stock symbol and one or more of the conditions. A >>stock symbol is required, but the others are not (You should of course >>require at list one, but that's a front end issue). >> >> >> >>HTH... >>Joe Webb >>SQL Server MVP >> >>~~~ >>Get up to speed quickly with SQLNS >>http://www.amazon.com/exec/obidos/tg/detail/-/0972688811 >> >> >> >>RDV wrote: >> >>>The examples tend to trigger off of absolute conditions. For example, >>>let me know when a stock price is > a value. Can you create a >>>subscription rule where the operator is included in the subscription? >>>For example, a single subscription template would allow you to >>>determine when the stock is <, >, = to a value. The user would choose >>>the operator when setting up the subscription. >>>What would this look like? >>>
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 |