Welcome to dbFreaks.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Why Notification Services?

 
   Database Help (Home) -> Notification Services RSS
Next:  Large Field in Event Definition  
Author Message
Mike Lopez2

External


Since: May 22, 2004
Posts: 1



(Msg. 1) Posted: Sat May 22, 2004 9:54 am
Post subject: Why Notification Services?
Archived from groups: microsoft>public>sqlserver>notificationsvcs (more info?)

Hello.

I've been looking for an enterprise-wide event publishing/subscription
solution for our internal Windows network that is similar to COM+ events.
I've posted questions in the "platformsdk.base" forum asking how this is
accomplished these days within the Windows platform - and got no response.

Is Notification Services the answer? And why is Microsoft bundling it with
SQL Server?

Maybe I should re-communicate my need: Our infrstructure consists of Win2000
server (soon to be Win2003), Active Directory, Exchange Server 2003, SQL
Server 2000, Outlook on all workstations and Win2000 Professional (minimum)
on all workstations. I want to develop our intranet so that users do not
have to remember to go and look for information. Rather I want to notify
pertinent users when there is information available that they need to know
about, and I want to make use of the features of Windows platform as much as
possible, thereby avoiding writing "plumbing" code..

In short, I want to send notifications from a server-hosted process to the
users when something happens, yet I don't want to just send them an email.
Rather I would rather have an application, that I develop, and that runs on
each users' machine to receive these notifications and perhaps flash an icon
in the task tray - or something like this. The problem for me to date is the
event infrastructure. If COM+ events had a broader scope than just the local
machine I would use it. But it doesn't.

So, is Notification Services the answer? What other Microsoft "technologies"
offer the same functionality, if any?

Thanks in advance,

Mike

 >> Stay informed about: Why Notification Services? 
Back to top
Login to vote
Joe Webb1

External


Since: Apr 28, 2004
Posts: 118



(Msg. 2) Posted: Tue May 25, 2004 11:30 am
Post subject: Re: Why Notification Services? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Mike -

In general SQL Server notification services is designed to much of what
you're describing. It's designed to recognize events from the outside
world and communicate their occurrence to subscribers - which is
basically what you described.

For your scenario there are, of course, some challenges that you will
need to address in your design.

First, how will SQLNS recognize an event? Are your events driven by
changes to a SQL Server database? Can they be produced, or at least
reproduced, as an XML document? You can, of course, develop your own
custom event provider to to recognize and create events within SQL
Server notification services.

Second, consider your subscribers. They will either need to sign up
directly with the application, or since you are and a very controlled
environment you may be able to import the users from the AD using ADSI.

Third, your delivery must be considered. It sounds like
very interactive desktop application that will recognize win
notifications have been generated. This is probably a custom delivery
channel to you will need to create using the .net framework. At its
simplest, this could be an application that runs on the desktop and
polls periodically for notifications for the subscriber. You can of
course extend this if you prefer. Or consider instant messaging.

If you haven't already done so, download notification services from the
Microsoft web site and go through the walk-through in books online.
Then take a look at the realtor example.

I hope this helps...
Joe Webb


Mike Lopez wrote:

 > Hello.
 >
 > I've been looking for an enterprise-wide event publishing/subscription
 > solution for our internal Windows network that is similar to COM+ events.
 > I've posted questions in the "platformsdk.base" forum asking how this is
 > accomplished these days within the Windows platform - and got no response.
 >
 > Is Notification Services the answer? And why is Microsoft bundling it with
 > SQL Server?
 >
 > Maybe I should re-communicate my need: Our infrstructure consists of Win2000
 > server (soon to be Win2003), Active Directory, Exchange Server 2003, SQL
 > Server 2000, Outlook on all workstations and Win2000 Professional (minimum)
 > on all workstations. I want to develop our intranet so that users do not
 > have to remember to go and look for information. Rather I want to notify
 > pertinent users when there is information available that they need to know
 > about, and I want to make use of the features of Windows platform as much as
 > possible, thereby avoiding writing "plumbing" code..
 >
 > In short, I want to send notifications from a server-hosted process to the
 > users when something happens, yet I don't want to just send them an email.
 > Rather I would rather have an application, that I develop, and that runs on
 > each users' machine to receive these notifications and perhaps flash an icon
 > in the task tray - or something like this. The problem for me to date is the
 > event infrastructure. If COM+ events had a broader scope than just the local
 > machine I would use it. But it doesn't.
 >
 > So, is Notification Services the answer? What other Microsoft "technologies"
 > offer the same functionality, if any?
 >
 > Thanks in advance,
 >
 > Mike
 >
 ><!-- ~MESSAGE_AFTER~ -->

 >> Stay informed about: Why Notification Services? 
Back to top
Login to vote
Mike74

External


Since: May 25, 2004
Posts: 3



(Msg. 3) Posted: Tue May 25, 2004 5:18 pm
Post subject: Re: Why Notification Services? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi, Joe, and thanks for responding.

Without knowing the details yet of NS, how it will recognize an event is
still a question for me. The changes most likely will not be driven by
changes to a SQL server database. I file being written to a directory could
be the source of an event, an incoming fax could also be an event. How does
NS recognize events, only in table changes? I guess a better question is,
what is a NS event?

Subscribers will have the ability to subscribe to events via the desktop
application(s).

As to delivery, from the first few articles I've read on NS, a channel needs
to be created. I don't know the details but if NS is supposed to be an
enterprise event/subscription service shouldn't it provide everything I
need? I guess the question comes back to what a NS event is. The idea is to
not poll, hence the usage of publishing/subscribing to events.

All input is welcome.

Thanks again,

Mike

"Joe Webb" <joew RemoveThis @webbtechsolutions.com> wrote in message
news:%23PRdzolQEHA.368@TK2MSFTNGP09.phx.gbl...
 > Mike -
 >
 > In general SQL Server notification services is designed to much of what
 > you're describing. It's designed to recognize events from the outside
 > world and communicate their occurrence to subscribers - which is
 > basically what you described.
 >
 > For your scenario there are, of course, some challenges that you will
 > need to address in your design.
 >
 > First, how will SQLNS recognize an event? Are your events driven by
 > changes to a SQL Server database? Can they be produced, or at least
 > reproduced, as an XML document? You can, of course, develop your own
 > custom event provider to to recognize and create events within SQL
 > Server notification services.
 >
 > Second, consider your subscribers. They will either need to sign up
 > directly with the application, or since you are and a very controlled
 > environment you may be able to import the users from the AD using ADSI.
 >
 > Third, your delivery must be considered. It sounds like
 > very interactive desktop application that will recognize win
 > notifications have been generated. This is probably a custom delivery
 > channel to you will need to create using the .net framework. At its
 > simplest, this could be an application that runs on the desktop and
 > polls periodically for notifications for the subscriber. You can of
 > course extend this if you prefer. Or consider instant messaging.
 >
 > If you haven't already done so, download notification services from the
 > Microsoft web site and go through the walk-through in books online.
 > Then take a look at the realtor example.
 >
 > I hope this helps...
 > Joe Webb
 >
 >
 > Mike Lopez wrote:
 >
  > > Hello.
  > >
  > > I've been looking for an enterprise-wide event publishing/subscription
  > > solution for our internal Windows network that is similar to COM+
events.
  > > I've posted questions in the "platformsdk.base" forum asking how this is
  > > accomplished these days within the Windows platform - and got no
response.
  > >
  > > Is Notification Services the answer? And why is Microsoft bundling it
with
  > > SQL Server?
  > >
  > > Maybe I should re-communicate my need: Our infrstructure consists of
Win2000
  > > server (soon to be Win2003), Active Directory, Exchange Server 2003, SQL
  > > Server 2000, Outlook on all workstations and Win2000 Professional
(minimum)
  > > on all workstations. I want to develop our intranet so that users do not
  > > have to remember to go and look for information. Rather I want to notify
  > > pertinent users when there is information available that they need to
know
  > > about, and I want to make use of the features of Windows platform as
much as
  > > possible, thereby avoiding writing "plumbing" code..
  > >
  > > In short, I want to send notifications from a server-hosted process to
the
  > > users when something happens, yet I don't want to just send them an
email.
  > > Rather I would rather have an application, that I develop, and that runs
on
  > > each users' machine to receive these notifications and perhaps flash an
icon
  > > in the task tray - or something like this. The problem for me to date is
the
  > > event infrastructure. If COM+ events had a broader scope than just the
local
  > > machine I would use it. But it doesn't.
  > >
  > > So, is Notification Services the answer? What other Microsoft
"technologies"
  > > offer the same functionality, if any?
  > >
  > > Thanks in advance,
  > >
  > > Mike
  > >
  > ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why Notification Services? 
Back to top
Login to vote
Joe Webb1

External


Since: Apr 28, 2004
Posts: 118



(Msg. 4) Posted: Wed May 26, 2004 10:24 am
Post subject: Re: Why Notification Services? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi Mike -

There are two standard of the providers that come with SQL Server
notification services: the SQL Server event provider in the
FileSystemWatcher. The SQL Server event provider periodically checks a
specified table or view using a query that you develop. The
FileSystemWatcher event provider constantly monitors a specified folder
for the addition of a new XML document that contains one or more events.
Both of these will likely be helpful to you.

If neither of these however are sufficient for your purposes, you can
develop your own custom event providers using the framework provided. A
very simple one can be developed as a trigger in a remote table that
calls some stored procedures in the application database.

Subscriber management objects (SMO) can be used by an application, the
head web or desktop, to add subscribers to the notification application.

Some delivery channels are provided with SQL Server notification
services. Again if they are not sufficient for your purposes you can
develop your own custom channels or custom content formatters to meet
your needs.

Although the examples are quite lacking in many respects, they offer
some good basic and foundational information goal helped to jumpstart a
project.

HTH...
Joe Webb



Mike wrote:

 > Hi, Joe, and thanks for responding.
 >
 > Without knowing the details yet of NS, how it will recognize an event is
 > still a question for me. The changes most likely will not be driven by
 > changes to a SQL server database. I file being written to a directory could
 > be the source of an event, an incoming fax could also be an event. How does
 > NS recognize events, only in table changes? I guess a better question is,
 > what is a NS event?
 >
 > Subscribers will have the ability to subscribe to events via the desktop
 > application(s).
 >
 > As to delivery, from the first few articles I've read on NS, a channel needs
 > to be created. I don't know the details but if NS is supposed to be an
 > enterprise event/subscription service shouldn't it provide everything I
 > need? I guess the question comes back to what a NS event is. The idea is to
 > not poll, hence the usage of publishing/subscribing to events.
 >
 > All input is welcome.
 >
 > Thanks again,
 >
 > Mike
 >
 > "Joe Webb" <joew.TakeThisOut@webbtechsolutions.com> wrote in message
 > news:%23PRdzolQEHA.368@TK2MSFTNGP09.phx.gbl...
 >
  >>Mike -
  >>
  >>In general SQL Server notification services is designed to much of what
  >>you're describing. It's designed to recognize events from the outside
  >>world and communicate their occurrence to subscribers - which is
  >>basically what you described.
  >>
  >>For your scenario there are, of course, some challenges that you will
  >>need to address in your design.
  >>
  >>First, how will SQLNS recognize an event? Are your events driven by
  >>changes to a SQL Server database? Can they be produced, or at least
  >>reproduced, as an XML document? You can, of course, develop your own
  >>custom event provider to to recognize and create events within SQL
  >>Server notification services.
  >>
  >>Second, consider your subscribers. They will either need to sign up
  >>directly with the application, or since you are and a very controlled
  >>environment you may be able to import the users from the AD using ADSI.
  >>
  >>Third, your delivery must be considered. It sounds like
  >>very interactive desktop application that will recognize win
  >>notifications have been generated. This is probably a custom delivery
  >>channel to you will need to create using the .net framework. At its
  >>simplest, this could be an application that runs on the desktop and
  >>polls periodically for notifications for the subscriber. You can of
  >>course extend this if you prefer. Or consider instant messaging.
  >>
  >>If you haven't already done so, download notification services from the
  >>Microsoft web site and go through the walk-through in books online.
  >>Then take a look at the realtor example.
  >>
  >>I hope this helps...
  >>Joe Webb
  >>
  >>
  >>Mike Lopez wrote:
  >>
  >>
   >>>Hello.
   >>>
   >>>I've been looking for an enterprise-wide event publishing/subscription
   >>>solution for our internal Windows network that is similar to COM+
 >
 > events.
 >
   >>>I've posted questions in the "platformsdk.base" forum asking how this is
   >>>accomplished these days within the Windows platform - and got no
 >
 > response.
 >
   >>>Is Notification Services the answer? And why is Microsoft bundling it
 >
 > with
 >
   >>>SQL Server?
   >>>
   >>>Maybe I should re-communicate my need: Our infrstructure consists of
 >
 > Win2000
 >
   >>>server (soon to be Win2003), Active Directory, Exchange Server 2003, SQL
   >>>Server 2000, Outlook on all workstations and Win2000 Professional
 >
 > (minimum)
 >
   >>>on all workstations. I want to develop our intranet so that users do not
   >>>have to remember to go and look for information. Rather I want to notify
   >>>pertinent users when there is information available that they need to
 >
 > know
 >
   >>>about, and I want to make use of the features of Windows platform as
 >
 > much as
 >
   >>>possible, thereby avoiding writing "plumbing" code..
   >>>
   >>> In short, I want to send notifications from a server-hosted process to
 >
 > the
 >
   >>>users when something happens, yet I don't want to just send them an
 >
 > email.
 >
   >>>Rather I would rather have an application, that I develop, and that runs
 >
 > on
 >
   >>>each users' machine to receive these notifications and perhaps flash an
 >
 > icon
 >
   >>>in the task tray - or something like this. The problem for me to date is
 >
 > the
 >
   >>>event infrastructure. If COM+ events had a broader scope than just the
 >
 > local
 >
   >>>machine I would use it. But it doesn't.
   >>>
   >>>So, is Notification Services the answer? What other Microsoft
 >
 > "technologies"
 >
   >>>offer the same functionality, if any?
   >>>
   >>>Thanks in advance,
   >>>
   >>>Mike
   >>>
   >>>
 >
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why Notification Services? 
Back to top
Login to vote
Mike74

External


Since: May 25, 2004
Posts: 3



(Msg. 5) Posted: Wed May 26, 2004 1:19 pm
Post subject: Re: Why Notification Services? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi Joe.

Thanks for the elaboration. It cleared up a couple of things.

I'm going to start diving into this stuff.

Thanks again,

Mike

"Joe Webb" <joew RemoveThis @webbtechsolutions.com> wrote in message
news:eETktoxQEHA.2404@TK2MSFTNGP09.phx.gbl...
 > Hi Mike -
 >
 > There are two standard of the providers that come with SQL Server
 > notification services: the SQL Server event provider in the
 > FileSystemWatcher. The SQL Server event provider periodically checks a
 > specified table or view using a query that you develop. The
 > FileSystemWatcher event provider constantly monitors a specified folder
 > for the addition of a new XML document that contains one or more events.
 > Both of these will likely be helpful to you.
 >
 > If neither of these however are sufficient for your purposes, you can
 > develop your own custom event providers using the framework provided. A
 > very simple one can be developed as a trigger in a remote table that
 > calls some stored procedures in the application database.
 >
 > Subscriber management objects (SMO) can be used by an application, the
 > head web or desktop, to add subscribers to the notification application.
 >
 > Some delivery channels are provided with SQL Server notification
 > services. Again if they are not sufficient for your purposes you can
 > develop your own custom channels or custom content formatters to meet
 > your needs.
 >
 > Although the examples are quite lacking in many respects, they offer
 > some good basic and foundational information goal helped to jumpstart a
 > project.
 >
 > HTH...
 > Joe Webb
 >
 >
 >
 > Mike wrote:
 >
  > > Hi, Joe, and thanks for responding.
  > >
  > > Without knowing the details yet of NS, how it will recognize an event is
  > > still a question for me. The changes most likely will not be driven by
  > > changes to a SQL server database. I file being written to a directory
could
  > > be the source of an event, an incoming fax could also be an event. How
does
  > > NS recognize events, only in table changes? I guess a better question
is,
  > > what is a NS event?
  > >
  > > Subscribers will have the ability to subscribe to events via the desktop
  > > application(s).
  > >
  > > As to delivery, from the first few articles I've read on NS, a channel
needs
  > > to be created. I don't know the details but if NS is supposed to be an
  > > enterprise event/subscription service shouldn't it provide everything I
  > > need? I guess the question comes back to what a NS event is. The idea is
to
  > > not poll, hence the usage of publishing/subscribing to events.
  > >
  > > All input is welcome.
  > >
  > > Thanks again,
  > >
  > > Mike
  > >
  > > "Joe Webb" <joew RemoveThis @webbtechsolutions.com> wrote in message
  > > news:%23PRdzolQEHA.368@TK2MSFTNGP09.phx.gbl...
  > >
   > >>Mike -
   > >>
   > >>In general SQL Server notification services is designed to much of what
   > >>you're describing. It's designed to recognize events from the outside
   > >>world and communicate their occurrence to subscribers - which is
   > >>basically what you described.
   > >>
   > >>For your scenario there are, of course, some challenges that you will
   > >>need to address in your design.
   > >>
   > >>First, how will SQLNS recognize an event? Are your events driven by
   > >>changes to a SQL Server database? Can they be produced, or at least
   > >>reproduced, as an XML document? You can, of course, develop your own
   > >>custom event provider to to recognize and create events within SQL
   > >>Server notification services.
   > >>
   > >>Second, consider your subscribers. They will either need to sign up
   > >>directly with the application, or since you are and a very controlled
   > >>environment you may be able to import the users from the AD using ADSI.
   > >>
   > >>Third, your delivery must be considered. It sounds like
   > >>very interactive desktop application that will recognize win
   > >>notifications have been generated. This is probably a custom delivery
   > >>channel to you will need to create using the .net framework. At its
   > >>simplest, this could be an application that runs on the desktop and
   > >>polls periodically for notifications for the subscriber. You can of
   > >>course extend this if you prefer. Or consider instant messaging.
   > >>
   > >>If you haven't already done so, download notification services from the
   > >>Microsoft web site and go through the walk-through in books online.
   > >>Then take a look at the realtor example.
   > >>
   > >>I hope this helps...
   > >>Joe Webb
   > >>
   > >>
   > >>Mike Lopez wrote:
   > >>
   > >>
   > >>>Hello.
   > >>>
   > >>>I've been looking for an enterprise-wide event publishing/subscription
   > >>>solution for our internal Windows network that is similar to COM+
  > >
  > > events.
  > >
   > >>>I've posted questions in the "platformsdk.base" forum asking how this
is
   > >>>accomplished these days within the Windows platform - and got no
  > >
  > > response.
  > >
   > >>>Is Notification Services the answer? And why is Microsoft bundling it
  > >
  > > with
  > >
   > >>>SQL Server?
   > >>>
   > >>>Maybe I should re-communicate my need: Our infrstructure consists of
  > >
  > > Win2000
  > >
   > >>>server (soon to be Win2003), Active Directory, Exchange Server 2003,
SQL
   > >>>Server 2000, Outlook on all workstations and Win2000 Professional
  > >
  > > (minimum)
  > >
   > >>>on all workstations. I want to develop our intranet so that users do
not
   > >>>have to remember to go and look for information. Rather I want to
notify
   > >>>pertinent users when there is information available that they need to
  > >
  > > know
  > >
   > >>>about, and I want to make use of the features of Windows platform as
  > >
  > > much as
  > >
   > >>>possible, thereby avoiding writing "plumbing" code..
   > >>>
   > >>> In short, I want to send notifications from a server-hosted process to
  > >
  > > the
  > >
   > >>>users when something happens, yet I don't want to just send them an
  > >
  > > email.
  > >
   > >>>Rather I would rather have an application, that I develop, and that
runs
  > >
  > > on
  > >
   > >>>each users' machine to receive these notifications and perhaps flash an
  > >
  > > icon
  > >
   > >>>in the task tray - or something like this. The problem for me to date
is
  > >
  > > the
  > >
   > >>>event infrastructure. If COM+ events had a broader scope than just the
  > >
  > > local
  > >
   > >>>machine I would use it. But it doesn't.
   > >>>
   > >>>So, is Notification Services the answer? What other Microsoft
  > >
  > > "technologies"
  > >
   > >>>offer the same functionality, if any?
   > >>>
   > >>>Thanks in advance,
   > >>>
   > >>>Mike
   > >>>
   > >>>
  > >
  > >
  > ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why Notification Services? 
Back to top
Login to vote
Joe Webb1

External


Since: Apr 28, 2004
Posts: 118



(Msg. 6) Posted: Wed May 26, 2004 1:19 pm
Post subject: Re: Why Notification Services? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hey Mike -

I just re-read my last posting. Sorry for the broken English. (Actually,
Americal English is my native language) For a few weeks now, I've been
using Dragon Naturally Speaking and am learning that I should carefully
review what I dictate before sending it - otherwise some
psuedo-gibberish can come out as happened this morning.

Anyway, I hope my prior post made sense and I'll be glad to continue the
conversation with you.

Joe Webb


Mike wrote:
 > Hi Joe.
 >
 > Thanks for the elaboration. It cleared up a couple of things.
 >
 > I'm going to start diving into this stuff.
 >
 > Thanks again,
 >
 > Mike
 >
 > "Joe Webb" <joew.RemoveThis@webbtechsolutions.com> wrote in message
 > news:eETktoxQEHA.2404@TK2MSFTNGP09.phx.gbl...
 >
  >>Hi Mike -
  >>
  >>There are two standard of the providers that come with SQL Server
  >>notification services: the SQL Server event provider in the
  >>FileSystemWatcher. The SQL Server event provider periodically checks a
  >>specified table or view using a query that you develop. The
  >>FileSystemWatcher event provider constantly monitors a specified folder
  >>for the addition of a new XML document that contains one or more events.
  >>Both of these will likely be helpful to you.
  >>
  >>If neither of these however are sufficient for your purposes, you can
  >>develop your own custom event providers using the framework provided. A
  >>very simple one can be developed as a trigger in a remote table that
  >>calls some stored procedures in the application database.
  >>
  >>Subscriber management objects (SMO) can be used by an application, the
  >>head web or desktop, to add subscribers to the notification application.
  >>
  >>Some delivery channels are provided with SQL Server notification
  >>services. Again if they are not sufficient for your purposes you can
  >>develop your own custom channels or custom content formatters to meet
  >>your needs.
  >>
  >>Although the examples are quite lacking in many respects, they offer
  >>some good basic and foundational information goal helped to jumpstart a
  >>project.
  >>
  >>HTH...
  >>Joe Webb
  >>
  >>
  >>
  >>Mike wrote:
  >>
  >>
   >>>Hi, Joe, and thanks for responding.
   >>>
   >>>Without knowing the details yet of NS, how it will recognize an event is
   >>>still a question for me. The changes most likely will not be driven by
   >>>changes to a SQL server database. I file being written to a directory
 >
 > could
 >
   >>>be the source of an event, an incoming fax could also be an event. How
 >
 > does
 >
   >>>NS recognize events, only in table changes? I guess a better question
 >
 > is,
 >
   >>>what is a NS event?
   >>>
   >>>Subscribers will have the ability to subscribe to events via the desktop
   >>>application(s).
   >>>
   >>>As to delivery, from the first few articles I've read on NS, a channel
 >
 > needs
 >
   >>>to be created. I don't know the details but if NS is supposed to be an
   >>>enterprise event/subscription service shouldn't it provide everything I
   >>>need? I guess the question comes back to what a NS event is. The idea is
 >
 > to
 >
   >>>not poll, hence the usage of publishing/subscribing to events.
   >>>
   >>>All input is welcome.
   >>>
   >>>Thanks again,
   >>>
   >>>Mike
   >>>
   >>>"Joe Webb" <joew.RemoveThis@webbtechsolutions.com> wrote in message
   >>>news:%23PRdzolQEHA.368@TK2MSFTNGP09.phx.gbl...
   >>>
   >>>
   >>>>Mike -
   >>>>
   >>>>In general SQL Server notification services is designed to much of what
   >>>>you're describing. It's designed to recognize events from the outside
   >>>>world and communicate their occurrence to subscribers - which is
   >>>>basically what you described.
   >>>>
   >>>>For your scenario there are, of course, some challenges that you will
   >>>>need to address in your design.
   >>>>
   >>>>First, how will SQLNS recognize an event? Are your events driven by
   >>>>changes to a SQL Server database? Can they be produced, or at least
   >>>>reproduced, as an XML document? You can, of course, develop your own
   >>>>custom event provider to to recognize and create events within SQL
   >>>>Server notification services.
   >>>>
   >>>>Second, consider your subscribers. They will either need to sign up
   >>>>directly with the application, or since you are and a very controlled
   >>>>environment you may be able to import the users from the AD using ADSI.
   >>>>
   >>>>Third, your delivery must be considered. It sounds like
   >>>>very interactive desktop application that will recognize win
   >>>>notifications have been generated. This is probably a custom delivery
   >>>>channel to you will need to create using the .net framework. At its
   >>>>simplest, this could be an application that runs on the desktop and
   >>>>polls periodically for notifications for the subscriber. You can of
   >>>>course extend this if you prefer. Or consider instant messaging.
   >>>>
   >>>>If you haven't already done so, download notification services from the
   >>>>Microsoft web site and go through the walk-through in books online.
   >>>>Then take a look at the realtor example.
   >>>>
   >>>>I hope this helps...
   >>>>Joe Webb
   >>>>
   >>>>
   >>>>Mike Lopez wrote:
   >>>>
   >>>>
   >>>>
   >>>>>Hello.
   >>>>>
   >>>>>I've been looking for an enterprise-wide event publishing/subscription
   >>>>>solution for our internal Windows network that is similar to COM+
   >>>
   >>>events.
   >>>
   >>>
   >>>>>I've posted questions in the "platformsdk.base" forum asking how this
 >
 > is
 >
   >>>>>accomplished these days within the Windows platform - and got no
   >>>
   >>>response.
   >>>
   >>>
   >>>>>Is Notification Services the answer? And why is Microsoft bundling it
   >>>
   >>>with
   >>>
   >>>
   >>>>>SQL Server?
   >>>>>
   >>>>>Maybe I should re-communicate my need: Our infrstructure consists of
   >>>
   >>>Win2000
   >>>
   >>>
   >>>>>server (soon to be Win2003), Active Directory, Exchange Server 2003,
 >
 > SQL
 >
   >>>>>Server 2000, Outlook on all workstations and Win2000 Professional
   >>>
   >>>(minimum)
   >>>
   >>>
   >>>>>on all workstations. I want to develop our intranet so that users do
 >
 > not
 >
   >>>>>have to remember to go and look for information. Rather I want to
 >
 > notify
 >
   >>>>>pertinent users when there is information available that they need to
   >>>
   >>>know
   >>>
   >>>
   >>>>>about, and I want to make use of the features of Windows platform as
   >>>
   >>>much as
   >>>
   >>>
   >>>>>possible, thereby avoiding writing "plumbing" code..
   >>>>>
   >>>>>In short, I want to send notifications from a server-hosted process to
   >>>
   >>>the
   >>>
   >>>
   >>>>>users when something happens, yet I don't want to just send them an
   >>>
   >>>email.
   >>>
   >>>
   >>>>>Rather I would rather have an application, that I develop, and that
 >
 > runs
 >
   >>>on
   >>>
   >>>
   >>>>>each users' machine to receive these notifications and perhaps flash an
   >>>
   >>>icon
   >>>
   >>>
   >>>>>in the task tray - or something like this. The problem for me to date
 >
 > is
 >
   >>>the
   >>>
   >>>
   >>>>>event infrastructure. If COM+ events had a broader scope than just the
   >>>
   >>>local
   >>>
   >>>
   >>>>>machine I would use it. But it doesn't.
   >>>>>
   >>>>>So, is Notification Services the answer? What other Microsoft
   >>>
   >>>"technologies"
   >>>
   >>>
   >>>>>offer the same functionality, if any?
   >>>>>
   >>>>>Thanks in advance,
   >>>>>
   >>>>>Mike
   >>>>>
   >>>>>
   >>>
   >>>
   >>>
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why Notification Services? 
Back to top
Login to vote
Mike74

External


Since: May 25, 2004
Posts: 3



(Msg. 7) Posted: Thu Jun 03, 2004 2:08 pm
Post subject: Re: Why Notification Services? [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Hi, Joe. Can I ask you another question?

Does NS compete with Biztalk in the event/messaging area? I understand that
BizTalk is much more.

Thanks again,

Mike

"Joe Webb" <joew.RemoveThis@webbtechsolutions.com> wrote in message
news:ecuBDDzQEHA.3532@TK2MSFTNGP12.phx.gbl...
 > Hey Mike -
 >
 > I just re-read my last posting. Sorry for the broken English. (Actually,
 > Americal English is my native language) For a few weeks now, I've been
 > using Dragon Naturally Speaking and am learning that I should carefully
 > review what I dictate before sending it - otherwise some
 > psuedo-gibberish can come out as happened this morning.
 >
 > Anyway, I hope my prior post made sense and I'll be glad to continue the
 > conversation with you.
 >
 > Joe Webb
 >
 >
 > Mike wrote:
  > > Hi Joe.
  > >
  > > Thanks for the elaboration. It cleared up a couple of things.
  > >
  > > I'm going to start diving into this stuff.
  > >
  > > Thanks again,
  > >
  > > Mike
  > >
  > > "Joe Webb" <joew.RemoveThis@webbtechsolutions.com> wrote in message
  > > news:eETktoxQEHA.2404@TK2MSFTNGP09.phx.gbl...
  > >
   > >>Hi Mike -
   > >>
   > >>There are two standard of the providers that come with SQL Server
   > >>notification services: the SQL Server event provider in the
   > >>FileSystemWatcher. The SQL Server event provider periodically checks a
   > >>specified table or view using a query that you develop. The
   > >>FileSystemWatcher event provider constantly monitors a specified folder
   > >>for the addition of a new XML document that contains one or more events.
   > >>Both of these will likely be helpful to you.
   > >>
   > >>If neither of these however are sufficient for your purposes, you can
   > >>develop your own custom event providers using the framework provided. A
   > >>very simple one can be developed as a trigger in a remote table that
   > >>calls some stored procedures in the application database.
   > >>
   > >>Subscriber management objects (SMO) can be used by an application, the
   > >>head web or desktop, to add subscribers to the notification application.
   > >>
   > >>Some delivery channels are provided with SQL Server notification
   > >>services. Again if they are not sufficient for your purposes you can
   > >>develop your own custom channels or custom content formatters to meet
   > >>your needs.
   > >>
   > >>Although the examples are quite lacking in many respects, they offer
   > >>some good basic and foundational information goal helped to jumpstart a
   > >>project.
   > >>
   > >>HTH...
   > >>Joe Webb
   > >>
   > >>
   > >>
   > >>Mike wrote:
   > >>
   > >>
   > >>>Hi, Joe, and thanks for responding.
   > >>>
   > >>>Without knowing the details yet of NS, how it will recognize an event
is
   > >>>still a question for me. The changes most likely will not be driven by
   > >>>changes to a SQL server database. I file being written to a directory
  > >
  > > could
  > >
   > >>>be the source of an event, an incoming fax could also be an event. How
  > >
  > > does
  > >
   > >>>NS recognize events, only in table changes? I guess a better question
  > >
  > > is,
  > >
   > >>>what is a NS event?
   > >>>
   > >>>Subscribers will have the ability to subscribe to events via the
desktop
   > >>>application(s).
   > >>>
   > >>>As to delivery, from the first few articles I've read on NS, a channel
  > >
  > > needs
  > >
   > >>>to be created. I don't know the details but if NS is supposed to be an
   > >>>enterprise event/subscription service shouldn't it provide everything I
   > >>>need? I guess the question comes back to what a NS event is. The idea
is
  > >
  > > to
  > >
   > >>>not poll, hence the usage of publishing/subscribing to events.
   > >>>
   > >>>All input is welcome.
   > >>>
   > >>>Thanks again,
   > >>>
   > >>>Mike
   > >>>
   > >>>"Joe Webb" <joew.RemoveThis@webbtechsolutions.com> wrote in message
   > >>>news:%23PRdzolQEHA.368@TK2MSFTNGP09.phx.gbl...
   > >>>
   > >>>
   > >>>>Mike -
   > >>>>
   > >>>>In general SQL Server notification services is designed to much of
what
   > >>>>you're describing. It's designed to recognize events from the outside
   > >>>>world and communicate their occurrence to subscribers - which is
   > >>>>basically what you described.
   > >>>>
   > >>>>For your scenario there are, of course, some challenges that you will
   > >>>>need to address in your design.
   > >>>>
   > >>>>First, how will SQLNS recognize an event? Are your events driven by
   > >>>>changes to a SQL Server database? Can they be produced, or at least
   > >>>>reproduced, as an XML document? You can, of course, develop your own
   > >>>>custom event provider to to recognize and create events within SQL
   > >>>>Server notification services.
   > >>>>
   > >>>>Second, consider your subscribers. They will either need to sign up
   > >>>>directly with the application, or since you are and a very controlled
   > >>>>environment you may be able to import the users from the AD using
ADSI.
   > >>>>
   > >>>>Third, your delivery must be considered. It sounds like
   > >>>>very interactive desktop application that will recognize win
   > >>>>notifications have been generated. This is probably a custom delivery
   > >>>>channel to you will need to create using the .net framework. At its
   > >>>>simplest, this could be an application that runs on the desktop and
   > >>>>polls periodically for notifications for the subscriber. You can of
   > >>>>course extend this if you prefer. Or consider instant messaging.
   > >>>>
   > >>>>If you haven't already done so, download notification services from
the
   > >>>>Microsoft web site and go through the walk-through in books online.
   > >>>>Then take a look at the realtor example.
   > >>>>
   > >>>>I hope this helps...
   > >>>>Joe Webb
   > >>>>
   > >>>>
   > >>>>Mike Lopez wrote:
   > >>>>
   > >>>>
   > >>>>
   > >>>>>Hello.
   > >>>>>
   > >>>>>I've been looking for an enterprise-wide event
publishing/subscription
   > >>>>>solution for our internal Windows network that is similar to COM+
   > >>>
   > >>>events.
   > >>>
   > >>>
   > >>>>>I've posted questions in the "platformsdk.base" forum asking how this
  > >
  > > is
  > >
   > >>>>>accomplished these days within the Windows platform - and got no
   > >>>
   > >>>response.
   > >>>
   > >>>
   > >>>>>Is Notification Services the answer? And why is Microsoft bundling it
   > >>>
   > >>>with
   > >>>
   > >>>
   > >>>>>SQL Server?
   > >>>>>
   > >>>>>Maybe I should re-communicate my need: Our infrstructure consists of
   > >>>
   > >>>Win2000
   > >>>
   > >>>
   > >>>>>server (soon to be Win2003), Active Directory, Exchange Server 2003,
  > >
  > > SQL
  > >
   > >>>>>Server 2000, Outlook on all workstations and Win2000 Professional
   > >>>
   > >>>(minimum)
   > >>>
   > >>>
   > >>>>>on all workstations. I want to develop our intranet so that users do
  > >
  > > not
  > >
   > >>>>>have to remember to go and look for information. Rather I want to
  > >
  > > notify
  > >
   > >>>>>pertinent users when there is information available that they need to
   > >>>
   > >>>know
   > >>>
   > >>>
   > >>>>>about, and I want to make use of the features of Windows platform as
   > >>>
   > >>>much as
   > >>>
   > >>>
   > >>>>>possible, thereby avoiding writing "plumbing" code..
   > >>>>>
   > >>>>>In short, I want to send notifications from a server-hosted process
to
   > >>>
   > >>>the
   > >>>
   > >>>
   > >>>>>users when something happens, yet I don't want to just send them an
   > >>>
   > >>>email.
   > >>>
   > >>>
   > >>>>>Rather I would rather have an application, that I develop, and that
  > >
  > > runs
  > >
   > >>>on
   > >>>
   > >>>
   > >>>>>each users' machine to receive these notifications and perhaps flash
an
   > >>>
   > >>>icon
   > >>>
   > >>>
   > >>>>>in the task tray - or something like this. The problem for me to date
  > >
  > > is
  > >
   > >>>the
   > >>>
   > >>>
   > >>>>>event infrastructure. If COM+ events had a broader scope than just
the
   > >>>
   > >>>local
   > >>>
   > >>>
   > >>>>>machine I would use it. But it doesn't.
   > >>>>>
   > >>>>>So, is Notification Services the answer? What other Microsoft
   > >>>
   > >>>"technologies"
   > >>>
   > >>>
   > >>>>>offer the same functionality, if any?
   > >>>>>
   > >>>>>Thanks in advance,
   > >>>>>
   > >>>>>Mike
   > >>>>>
   > >>>>>
   > >>>
   > >>>
   > >>>
  > >
  > ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why Notification Services? 
Back to top
Login to vote
Display posts from previous:   
   Database Help (Home) -> Notification Services All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]