Working mostly with Stored Procedures in RDBMS.

I have few queries regarding the use of Stored Procedures, Functions
and Triggers in an RDBMS.

(1) When to use Stored Procedure? Writing an INSERT query in a Stored
Procedure is better or firing it from the application level?

(2) Can a Trigger call a Stored Procedure?

(3) What type of code must reside in application and what type in
RDBMS?

(4) Is it faster to work at application level or at the database level?

.

Relevant Pages

  • Re: buffer overrun
    ... In Query Analyzer press "CTRL+K" to enable "Show Execution Plan" that look ... That table has 2 update triggers, ... Running the same stored procedure ...
    (microsoft.public.sqlserver.programming)
  • Re: BLL & DAL: How are they different?
    ... stored procedure names which are used in the DAL. ... So long as your DAL is capable of interfacing with SQL Server (either because that's the only RDBMS it supports or because it uses a factory pattern), you should simply be able to drop your DAL into both projects without modification. ... foreach (SqlParameter objSqlParameter in plstSqlParameters) ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Working mostly with Stored Procedures in RDBMS.
    ... and Triggers in an RDBMS. ... Can a Trigger call a Stored Procedure? ... the DB it's easier - although some tools can handle the DB and clients ...
    (comp.databases)
  • Re: BLL & DAL: How are they different?
    ... And what if you aren't a stored procedure person...? ... the DAL code only, right? ... Depends on the RDBMS but, for SQL Server, I use the SqlParameters ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Retrieving Stored Procedure Returns
    ... >CallableStatement after executing a Stored procedure. ... The RDBMS is MS ... the name spGetNextBatch makes the think there's an actual return value ...
    (comp.lang.java.programmer)