"Joe Webb1" wrote:
> Hi wqdeng -
>
> Notification Services has very flexible deployment options.
> For small to
> medium deployments you can put everything on one box. This is
> especially
> good for testing and in-house applications, but not really
> advisable for
> Internet applications.
>
> For slightly larger deployments you can use the remote
> database
> deployment option. This puts all of the Notification Services
> components
> on a single box and uses a remote SQL Server for the
> application and
> instance databases. The standard version of Notification
> Services
> supports this option.
>
> For larger deployments, you can use the scale out deployment
> option
> whereby various components can be installed across different
> servers.
>
> To collect events from another SQL Server database, you have a
> couple of
> options. First you can use the SQL Server event provider that
> comes with
> notification services. To do this I typically at a linked
> server in use
> four-part names when defining my configuration files.
>
> The second option uses the notification services event stored
> procedures. A trigger or stored procedure in the event-source
> database
> can call the event stored procedures and the NS database and
> submit
> events that way. Again a typically use a linked server to
> accomplish
> the cross server queries.
>
> Of course log shipping and other mechanisms would work, but
> they seem
> overly complex for this solution.
>
>
> HTH...
> Joe Webb
> SQL Server MVP
>
> ~~~
> Get up to speed quickly with SQLNS
> http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
>
>
>
>
> wqdeng wrote:
> > I need get data from source OLTP DB for NS DB. Putting NS DB
> and OLTP
> > DB on the same server will decrease performance too much
> which
> > Microsoft doesn’t suggest also. What’s the best way to
> seperate DB
> > from OLTP DB for NS, linked server, replication or anything
> else? Hope
> > someone can help me on it.
> >
> > Thanks,
> > Wenqing
> >

wqdeng wrote:
> "Joe Webb1" wrote:
> > Hi wqdeng -
> >
> > Notification Services has very flexible deployment options.
> > For small to
> > medium deployments you can put everything on one box. This is
> > especially
> > good for testing and in-house applications, but not really
> > advisable for
> > Internet applications.
> >
> > For slightly larger deployments you can use the remote
> > database
> > deployment option. This puts all of the Notification Services
> > components
> > on a single box and uses a remote SQL Server for the
> > application and
> > instance databases. The standard version of Notification
> > Services
> > supports this option.
> >
> > For larger deployments, you can use the scale out deployment
> > option
> > whereby various components can be installed across different
> > servers.
> >
> > To collect events from another SQL Server database, you have a
> > couple of
> > options. First you can use the SQL Server event provider that
> > comes with
> > notification services. To do this I typically at a linked
> > server in use
> > four-part names when defining my configuration files.
> >
> > The second option uses the notification services event stored
> > procedures. A trigger or stored procedure in the event-source
> > database
> > can call the event stored procedures and the NS database and
> > submit
> > events that way. Again a typically use a linked server to
> > accomplish
> > the cross server queries.
> >
> > Of course log shipping and other mechanisms would work, but
> > they seem
> > overly complex for this solution.
> >
> >
> > HTH...
> > Joe Webb
> > SQL Server MVP
> >
> > ~~~
> > Get up to speed quickly with SQLNS
> > http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
> >
> >
> >
> >
> > wqdeng wrote:
> > > I need get data from source OLTP DB for NS DB. Putting NS DB
> > and OLTP
> > > DB on the same server will decrease performance too much
> > which
> > > Microsoft doesn’t suggest also. What’s the best way to
> > seperate DB
> > > from OLTP DB for NS, linked server, replication or anything
> > else? Hope
> > > someone can help me on it.
> > >
> > > Thanks,
> > > Wenqing
> > >
>
> Joe,
>
> Thanks for your information. My case is fallen into your larger
> deployments case. I tested performance of linked server. For a simple
> two tables join, it took less than one second to finish locally,
> however more than one and half minute for linked server. The
> difference is huge. I am afraid that linked server can handle our
> large volume tasks. Do you have any suggestion for larger deployments?
> How about replication?
>
> Thanks,
> Wenqing