"Mike Saunders" <enquiries@folleytech.co.uk> wrote in message
news:OQMNdAnaHHA.4808@TK2MSFTNGP04.phx.gbl...
>
> I am not familiar with SQL Server but need to know how the following
> scenario would be satsified
>
> A user registers his details online to a server somewhere. Another
> server elswhere however also needs to be notified of this transaction
> as well as store some of the original data The 2nd server then
> generates a registration No which is then sent back the first server
> where it is presented to the user All this to be transparent and
> seamless
>
> I would like to know as precisely as possible how this could be done so
> we may formulate our requirement
>
> Many thanks
>
> Mike
>
>
>
>
>
>
>

"Kevin G. Boles" <kgboles@earthlink.net> wrote in message
news:O63qgPnaHHA.588@TK2MSFTNGP06.phx.gbl...
> 1) Use a trigger on server 1 to send INSERTed data to the second server,
> which also has a trigger to send generated data back to server 1.
>
> 2) Have your code set up to do one distributed transaction referencing
both
> servers as necessary in turn.
>
> 3) more obtuse solutions can be developed using Service Manager and/or
> Message Queues.
>
>
>
> --
> TheSQLGuru
> President
> Indicium Resources, Inc.
> "Mike Saunders" <enquiries@folleytech.co.uk> wrote in message
> news:OQMNdAnaHHA.4808@TK2MSFTNGP04.phx.gbl...
> >
> > I am not familiar with SQL Server but need to know how the following
> > scenario would be satsified
> >
> > A user registers his details online to a server somewhere. Another
> > server elswhere however also needs to be notified of this transaction
> > as well as store some of the original data The 2nd server then
> > generates a registration No which is then sent back the first server
> > where it is presented to the user All this to be transparent and
> > seamless
> >
> > I would like to know as precisely as possible how this could be done so
> > we may formulate our requirement
> >
> > Many thanks
> >
> > Mike
> >
> >
> >
> >
> >
> >
> >
>
>