Hi,
I think what the original query meant was that the sqlpreview processing of
the dw will be overridden, and instead a corresponding sp will be called
with the right payload - one for insert,one for delete and one for update.
The select sp will be the datasource. The programmer has to do some
processing for each row to determine which sp to call.
If the dw is a simple single table dw, then you can even specify the table
name in update properties, and it still works.
As regards the advantages, I am not entirely convinced about how helpful it
really can be (except if the select query is highly complex when the
precompiled sp is good).
I have not benchmarked updates against the dw update. I do however feel that
sp updates may not be significantly beter since the dw itself does a similar
thing - row wise insert, delete or update.
Perhaps if the business logic is is back end oriented, it may make sense.
However if that is not the case, it may be better to let the dw do what it's
best at - data management.
If anyone has more input on the performance issues, please share it with the
rest of us.
Sanjay.
>From: Peter Brawley <[EMAIL PROTECTED]>
>To: Dario Schmidt <[EMAIL PROTECTED]>
>CC: Lista PFC <[EMAIL PROTECTED]>
>Subject: Re: PFCSIG Stored procedures
>Date: Mon, 30 Aug 1999 09:11:44 -0700
>
>The sqlPreview event is used to modify a datawindow's sql syntax. If the
>DW's
>retieval is accomplished by an SP however, the DW's syntax is hidden in the
>SP so
>isn't acccessible to the sqlPreview event.
>
>You can configure DWs to retrieve via SPs but you thereby lose some DW
>power &
>flexibility. We use SPs to implement custom database operations & business
>rules.
>
>(Since many of us belong to multiple lists, it's best to post a question to
>one list
>at a time.)
>
>P.
>
>-----------
>
>Dario Schmidt wrote:
>
> > Hello,
> >
> > I am to begin a project of great span. I need help regarding the use of
> > stored procedures. In my previous projects I have used stored procedures
>to
> > recover information of the database, while it lets that all the
>operations
> > of maintenance are managed by the datawindow.
> >
> > I want to know which are the advantages and disadvantages of using
>stored
> > procedures for the operations of maintenance.
> >
> > I think that the use of stored procedures possesses the following
> > advantages:
> > * Security. The permits are granted on the stored procedures and don't
>on
> > the tables that these they maintain.
> > * Logic: possibility to include business rules inside the stored
>procedures.
> > * Performance.
> >
> > In the case that is convenient the use of stored procedures, my idea is
>to
> > use the event sqlpreview to invoke to the stored corresponding
>procedure. Is
> > this correct?
> >
> > The application will be developed with PB 6.5 and PFC. The databases
>will be
> > Sybase ASE and ASA.
> >
> > Thank you
> >
> > -----------------------------
> > Ing. Dario Schmidt
> > CERIDE - Santa Fe
> > Argentina
> > ----------------------------
> >
> > > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE
>COMMANDS, ADDRESS
> > > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help
>pfcsig
> > > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
>
> > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
>ADDRESS
> > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help
>pfcsig
> > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
