Equivalent to database events

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Chloe Crowder

    Equivalent to database events

    Hi

    we are considering porting an application from Ingres to SQL Server.
    Part of the application uses a feature of Ingres called database
    events. These allow a application to monitor for an event happening in
    the database, e.g. a user enters a record meeting certain conditions,
    the database raises an event including a record ID, and a client
    application sees the event (without continual explicit polling), reads
    the new record and starts processing it.

    Any idea what the equivalent functionality would be in SQL Server
    2000, or are applications simply not done that way?

    TIA

    Chloe Crowder
    The British Library
  • Greg D. Moore \(Strider\)

    #2
    Re: Equivalent to database events


    "Chloe Crowder" <chloe.crowder@ bl.uk> wrote in message
    news:f27559a3.0 312180743.4fc88 3ea@posting.goo gle.com...[color=blue]
    > Hi
    >
    > we are considering porting an application from Ingres to SQL Server.
    > Part of the application uses a feature of Ingres called database
    > events. These allow a application to monitor for an event happening in
    > the database, e.g. a user enters a record meeting certain conditions,
    > the database raises an event including a record ID, and a client
    > application sees the event (without continual explicit polling), reads
    > the new record and starts processing it.[/color]

    Sounds like you might be able to use INSERT/UPDATE/DELETE triggers.

    [color=blue]
    >
    > Any idea what the equivalent functionality would be in SQL Server
    > 2000, or are applications simply not done that way?
    >
    > TIA
    >
    > Chloe Crowder
    > The British Library[/color]


    Comment

    • Christian Maslen

      #3
      Re: Equivalent to database events

      > we are considering porting an application from Ingres to SQL Server.[color=blue]
      > Part of the application uses a feature of Ingres called database
      > events.[/color]

      Database events are one of the few things I've seen in Ingres that I'd
      never come across before. I don't think SQL Server 2000 has an
      equivalent feature, but looking at the feature list for Yukon it
      appears to be coming:



      Check out the paragraph on the SQL Service Broker.

      Christian.

      Comment

      • Joe Maloney

        #4
        Re: Equivalent to database events

        There are things called triggers ('on insert' in this case) that can
        kick off processing as you describe.

        There are other techniques available, but more information about your
        application/process would be needed before I put the other foot in my
        mouth.


        chloe.crowder@b l.uk (Chloe Crowder) wrote in message news:<f27559a3. 0312180743.4fc8 83ea@posting.go ogle.com>...[color=blue]
        > Hi
        >
        > we are considering porting an application from Ingres to SQL Server.
        > Part of the application uses a feature of Ingres called database
        > events. These allow a application to monitor for an event happening in
        > the database, e.g. a user enters a record meeting certain conditions,
        > the database raises an event including a record ID, and a client
        > application sees the event (without continual explicit polling), reads
        > the new record and starts processing it.
        >
        > Any idea what the equivalent functionality would be in SQL Server
        > 2000, or are applications simply not done that way?
        >
        > TIA
        >
        > Chloe Crowder
        > The British Library[/color]

        Comment

        • Chloe Crowder

          #5
          Re: Equivalent to database events

          christian.masle n@techie.com (Christian Maslen) wrote in message[color=blue]
          > Database events are one of the few things I've seen in Ingres that I'd
          > never come across before. I don't think SQL Server 2000 has an
          > equivalent feature, but looking at the feature list for Yukon it
          > appears to be coming:
          >
          > http://msdn.microsoft.com/library/de...ovyukondev.asp
          >
          > Check out the paragraph on the SQL Service Broker.
          >
          > Christian.[/color]

          Thanks for this Christian, it does look (at first glance) very similar
          to what we've been using in Ingres.

          Chloe

          Comment

          • Christian Maslen

            #6
            Re: Equivalent to database events

            chloe.crowder@b l.uk (Chloe Crowder) wrote in message news:<f27559a3. 0312190120.656c 1f4f@posting.go ogle.com>...[color=blue]
            > christian.masle n@techie.com (Christian Maslen) wrote in message[color=green]
            > > Database events are one of the few things I've seen in Ingres that I'd
            > > never come across before. I don't think SQL Server 2000 has an
            > > equivalent feature, but looking at the feature list for Yukon it
            > > appears to be coming:
            > >
            > > http://msdn.microsoft.com/library/de...ovyukondev.asp
            > >
            > > Check out the paragraph on the SQL Service Broker.
            > >
            > > Christian.[/color]
            >
            > Thanks for this Christian, it does look (at first glance) very similar
            > to what we've been using in Ingres.
            >
            > Chloe[/color]

            Are you just porting the DB and keeping OpenROAD? Or is it a complete
            rewrite? The closest you can get without waiting for Yukon is to use a
            message queuing package. I've not done anything in this area, but I
            think the MS option comes out of the box with Win2k servers.

            Christian.

            Comment

            Working...