What are Database Procedures? - Actian

More documents

Recommendations

Info

Why Use Database Procedures? Controls access to database objects– Only procedure owner requires privileges– Users only require execute on the procedure– Users do not require access to DBP objects Security is easier to manage– Data only changed via procedures– Less privileges– Easier still with roles and groups
What Not to Put in a DBP Unnecessary and complex code Unnecessary Variables Transaction control– Commit– Rollback Front-end work– Formatting data– Retry logic
Page 1 and 2: Smedley'sGuideToDatabaseProcedures
Page 3: Why Use Database Procedures? Perfor
Page 7 and 8: Parameter Passing By default Parame
Page 9 and 10: Locking Strategy Locks taken when p
Page 11: Procedure: get_my_airlinescreate pr
Page 15: How Big is a QEP?register table imp
Page 18 and 19: Example - Row Producing ProcedureEx
Page 20 and 21: Error BehaviourProcedure is not ter
Page 22 and 23: Return Terminates the procedure Can
Page 24 and 25: Raise Error StatementUsed to descri
Page 26 and 27: The Right Way to Error Check...upda
Page 28 and 29: The Wrong Way to Error Checkupdate
Page 30 and 31: Error Handling Simple is best Just
Page 32 and 33: Select Loopcreate procedure news_so
Page 34 and 35: Session tabledeclare global tempora
Page 36 and 37: Session tablebeginnext_id = 1;delet
Page 38 and 39: Comparison Advantages of rules and
Page 40 and 41: Error Behaviour for DBP invoked by
Page 42 and 43: Example of Before Rulecreate rule s

What are Database Procedures? - Actian

Create successful ePaper yourself

Delete template?

Save as template?