B4: DataServer Best Practices Revised & Revisited Noel Shannon Senior Solution Consultant.

B4: DataServer Best Practices Revised & Revisited Noel Shannon Senior Solution Consultant

© 2008 Progress Software Corporation 2 D I S C L A I M E R Under Development  This talk includes information about potential future products and/or product enhancements.  What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here. D I S C L A I M E R

© 2008 Progress Software Corporation 3 Agenda  DataServers & Best Practices The path to successful DataServer development & deployment Why ? When to use ? What are they ? Why ? When to use ? What are they ?

© 2008 Progress Software Corporation 4 DataServers: WHY ?  Has a customer, your partners or your company ever asked you: “Does your OpenEdge Application run against” MS SQL Server ? Oracle ® ? Some other data source ?

© 2008 Progress Software Corporation 5 DataServers WHEN ?  When “yes” on the WHY question would be compelling  “Yes” is “compelling” when there’s a willingness to: “Invest” mind share in the foreign data source Re-examine parts of your OpenEdge application Compromise performance for conformance … in light of a “compelling” business case, corporate decision or market opportunity.

© 2008 Progress Software Corporation 6 What is a DataServer ?  A “redirection” layer for database requests in an OpenEdge client or agent.  OpenEdge database request translation  Interface layer communication with a foreign data source

© 2008 Progress Software Corporation 13 What is a DataServer ? Oracle SQL Server Oracle SQL Server INTVARCHAR2 5L 6Ellison MS SQL Server MS SQL Server INTVARCHAR 3B 4Gates OpenEdge Database OpenEdge Database INTCHAR

© 2008 Progress Software Corporation 14 Agenda  DataServers & Best Practices The path to successful DataServer development & deployment Why √ When to use √ What are they √ Why ? When to use ? What are they ?

© 2008 Progress Software Corporation 16 WHY Use DataServer Best Practices ?  Appreciate: You are replacing the strengths of your OpenEdge Database with those of another data source: Deference is given to the foreign data source on: –Set-based SQL design –Cursor Consistency –Security –Transaction Control –Lock Management –Query Optimization & Indexing –Constraints

© 2008 Progress Software Corporation 17 WHY Use DataServer Best Practices ?  Appreciate: You are replacing the features of your OpenEdge Database with those of another data source: “Context” resides in the foreign data source for: –Data Types: Fixed versus variable length strings –Sequences, Triggers, Constraint implementations –Schema, Naming, Qualifying, Networking Conventions –NULLs versus UNKNOWNs –PL/SQL or T-SQL versus ABL

© 2008 Progress Software Corporation 20 WHEN To Use DataServer Best Practices ?  Conformance: Example Picking an Index FOR EACH customer: END. FOR EACH employee USE-INDEX department: END. FOR EACH invoice BY zip-code: END.

© 2008 Progress Software Corporation 21 WHEN To Use DataServer Best Practices ?  Performance: Example Who should do the join ? FOR EACH customer, EACH order OF customer QUERY-TUNING (NO-JOIN-BY-SQLDB): DISPLAY customer.name customer.cust-num customer.postal-code order.order-date. END.

© 2008 Progress Software Corporation 22 WHEN To Use DataServer Best Practices ?  Performance: Example What will be joined ? FOR EACH customer, EACH order OF customer WHERE LENGTH(RIGHT-TRIM(customer.name)) > 5: DISPLAY customer.name customer.cust-num customer.postal-code order.order-date. END.

© 2008 Progress Software Corporation 23 WHEN To Use DataServer Best Practices ?  Performance: Example Where is the join done ? FOR EACH customer, FIRST order OUTER-JOIN OF customer WHERE order.order-num < 50: DISPLAY customer.name customer.cust-num customer.postal-code order.order-date. END.

© 2008 Progress Software Corporation 24 WHAT are the DataServer Best Practices ? “Steps for Successful DataServer Development and Deployment”  http://www.psdn.com/library/entry.jspa?externalID=1320 http://www.psdn.com/library/entry.jspa?externalID=1320 (Located on PSDN) DataServer Guides  Chapter(s) on “Programming Considerations” The Best Practices White Paper

© 2008 Progress Software Corporation 25 WHAT are the DataServer Best Practices ? STEP ONE: Eliminate DBMS differences STEP TWO: Optimize the Application, the DataServer, and the DBMS. In the Best Practices White Paper …

© 2008 Progress Software Corporation 26 WHAT are the DataServer Best Practices ?  First get it to work Compile incompatibilities are minimal –SETUSERID –COUNT-OF –CONTAINS –RECID ** ** If ROWID index is not a unique integer STEP ONE: Eliminate DBMS differences

© 2008 Progress Software Corporation 27 WHAT are the DataServer Best Practices ?  Then there are the nuances … FIND cust WHERE name BEGINS “SI”. FOR EACH cust WHERE name <= CHR(126). FOR EACH cust WHERE name <> “Bob” STEP ONE: Eliminate DBMS differences

© 2008 Progress Software Corporation 28 WHAT are the DataServer Best Practices ?  Record Scoping & Availability STEP ONE: Eliminate DBMS differences DEFINE BUFFER xcust FOR cust. CREATE cust. ASSIGN cust-num = 111. FIND xcust WHERE cust.cust-num = 111.

© 2008 Progress Software Corporation 29 WHAT are the DataServer Best Practices ?  Record Scoping & Availability STEP ONE: Eliminate DBMS differences DEFINE BUFFER xcust FOR cust. CREATE cust. ASSIGN cust-num = 111. VALIDATE cust. FIND xcust WHERE cust.cust-num = 111.

© 2008 Progress Software Corporation 30 WHAT are the DataServer Best Practices ?  Record Scoping & capturing validation STEP ONE: Eliminate DBMS differences FOR FIRST cust EXCLUSIVE-LOCK: ASSIGN name = FILL(“a”,35) NO-ERROR. VALIDATE NO-ERROR. IF error-status:error THEN DO: UNDO, LEAVE. END. END.

© 2008 Progress Software Corporation 31 WHAT are the DataServer Best Practices ?  Record Scoping & Transactions STEP ONE: Eliminate DBMS differences DEF VAR num AS INT INIT 103. DO TRANSACTION: FIND cust WHERE cust = num EXCLUSIVE-LOCK. ASSIGN name = “Bob”. END. FIND cust WHERE cust-num = num. DISPLAY name.

© 2008 Progress Software Corporation 32 WHAT are the DataServer Best Practices ?  Record Scoping & Transactions STEP ONE: Eliminate DBMS differences DO TRANSACTION: FIND FIRST cust EXCLUSIVE-LOCK. END. RELEASE cust. DO TRANSACTION: FIND FIRST cust EXCLUSIVE-LOCK. END.

© 2008 Progress Software Corporation 33 WHAT are the DataServer Best Practices ?  Record Scoping & Transactions STEP ONE: Eliminate DBMS differences REPEAT: FIND FIRST cust. ASSIGN cust-num = 1. do-blk: DO ON ERROR UNDO do-blk, RETRY do-blk: FIND state WHERE st.st = cust.st. SET state. END. END. DISPLAY state.

© 2008 Progress Software Corporation 34 WHAT are the DataServer Best Practices ?  Record Scoping & Transactions STEP ONE: Eliminate DBMS differences REPEAT: FIND FIRST cust. ASSIGN cust-num = 1. do-blk: DO ON ERROR UNDO do-blk, RETRY do-blk: FIND state WHERE st.st = cust.st. SET state. VALIDATE state. END. END. DISPLAY state.

© 2008 Progress Software Corporation 35 WHAT are the DataServer Best Practices ?  Record Scoping & Visibility STEP ONE: Eliminate DBMS differences FOR FIRST cust NO-LOCK BY cust-num: END. IF AVAILABLE cust THEN MESSAGE “cust found” VIEW-AS ALERT-BOX.

© 2008 Progress Software Corporation 36 WHAT are the DataServer Best Practices ?  Record Scoping & Locking STEP ONE: Eliminate DBMS differences FOR FIRST cust: FOR FIRST cust NO-LOCK: FOR FIRST cust SHARE-LOCK: FOR FIRST cust EXCLUSIVE-LOCK:

© 2008 Progress Software Corporation 37 WHAT are the DataServer Best Practices ?  Record Scoping & Cursor Positioning STEP ONE: Eliminate DBMS differences FIND cust WHERE cust-num = 123. FIND cust WHERE name = “Bob”.

© 2008 Progress Software Corporation 38 WHAT are the DataServer Best Practices ?  Just code around certain nuances STEP ONE: Eliminate DBMS differences &GLOBAL-DEFINE DB-TYPE ORACLE &IF NOT DEFINED ({&MSSQLS}) &THEN … IF DBTYPE(dbname) = “PROGRESS” THEN RUN OpenEdge-database-code ELSE RUN DataServer-foreign-interface-code

© 2008 Progress Software Corporation 39 WHAT are the DataServer Best Practices ?  Be explicit about: Scope of your records Timing of your write operations STEP ONE: Eliminate DBMS differences VALIDATE RELEASE RECID

© 2008 Progress Software Corporation 40 WHAT are the DataServer Best Practices ?  Code knowing that for DataServers: Transactions narrow record scoping Transactions release locks and should release buffers STEP ONE: Eliminate DBMS differences DO TRANSACTION: ASSIGN cust.name = “Bob”. END. RELEASE cust.

© 2008 Progress Software Corporation 41 WHAT are the DataServer Best Practices ?  Avoid SHARE-LOCK  Adopt a “pessimistic“ locking model: –NO-LOCK –EXCLUSIVE-LOCK STEP ONE: Eliminate DBMS differences FOR EACH cust EXCLUSIVE-LOCK: ASSIGN name = “Bob”. END.

© 2008 Progress Software Corporation 42 WHAT are the DataServer Best Practices ?  DataServers only reposition FIND statement “cursors”. Set-based result statements are “contained”. FOR EACH QUERY DYNAMIC FIND  RELEASE set-based buffers that should be out of scope after these, STEP ONE: Eliminate DBMS differences FOR EACH cust: DISPLAY cust. END. RELEASE cust.

© 2008 Progress Software Corporation 45 WHAT are the DataServer Best Practices ? Consider the difference STEP ONE: Eliminate DBMS differences FIND customer USE-INDEX cust-num. versus FOR EACH customer BY cust-num.

© 2008 Progress Software Corporation 46 WHAT are the DataServer Best Practices ?  Code with a set-based mind set ! FOR EACH QUERY DYNAMIC FIND INDEXED-REPOSITION  Avoid OLTP-biased FIND statements STEP ONE: Eliminate DBMS differences

© 2008 Progress Software Corporation 48 WHAT are the DataServer Best Practices ? STEP TWO: Optimize the Application, the DataServer, and the DBMS. On PSDN, see “Performance Study” at the end of “DB-16: In Any Case, the Devil’s in the DataServer Details”: http://www.psdn.com/library/entry.jspa?externalID=3355 STEP ONE: Eliminate DBMS differences

© 2008 Progress Software Corporation 49 WHAT are the DataServer Best Practices ?  ROWID optimizes OpenEdge database access  DataServers map ROWID to a unique key  Uniqueness in DataServers enables: Locking Deletions & Updates FINDs, Queries & Browsers All cursor positioning such as INDEXED-REPOSITION RECID/ROWID functions random record access in a non-unique set STEP TWO: Optimize Application, DataServer, and DBMS.

© 2008 Progress Software Corporation 50 WHAT are the DataServer Best Practices ?  Set-based design enhances ROWID reconciliation FOR EACH QUERY DYNAMIC FIND INDEXED-REPOSITION STEP TWO: Optimize Application, DataServer, and DBMS.

© 2008 Progress Software Corporation 51 WHAT are the DataServer Best Practices ? #1. Eliminate FIND statements FIND FIRST cust FOR FIRST cust:END. FIND LAST cust FOR LAST cust:END. STEP TWO: Optimize Application, DataServer, and DBMS.

© 2008 Progress Software Corporation 52 WHAT are the DataServer Best Practices ? FIND FIRST Customer NO-LOCK NO-ERROR. IF AVAILABLE Customer THEN Cnt = 1. REPEAT: FIND NEXT Customer NO-ERROR. IF NOT AVAILABLE (Customer) THEN LEAVE. Cnt = Cnt + 1. END. OPEN QUERY q FOR EACH Customer NO-LOCK. REPEAT: GET NEXT q. IF NOT AVAILABLE Customer THEN LEAVE. Cnt = Cnt + 1. END. CLOSE QUERY q. STEP TWO: Optimize Application, DataServer, and DBMS.

© 2008 Progress Software Corporation 53 WHAT are the DataServer Best Practices ? #2: Stored Procedures #3: Avoid SHARE-LOCK, Consider NO-LOCK #4: Tune your database, especially indexes #5: Resolve queries/joins on the server #6: Use field lists and/or views #7: Use QUERY-TUNING where appropriate #8: Use –Dsrv connect options #9: Client startup options STEP TWO: Optimize Application, DataServer, and DBMS.

© 2008 Progress Software Corporation 55 For More Information, go to… Basic Tools:  Manual Refactoring (and 10.1C unsupported switch “-clw”) ???  Performance logs  Progress ® Debugger  Compile XREF  Progress Profiler Tool (unsupported but ships w/OpenEdge) Other Resources:  Proparse: http://www.joanju.comhttp://www.joanju.com  Prolint-http: http://www.prolint.orghttp://www.prolint.org  ProRefactor: http://www.prorefactor.orghttp://www.prorefactor.org  PSDN OpenEdge DataServers category (Best Practices paper, Performance Study)OpenEdge DataServers category Forum: OpenEdge RDBMS & Data Management Redevelopment Tools

B4: DataServer Best Practices Revised & Revisited Noel Shannon Senior Solution Consultant.

Similar presentations

Presentation on theme: "B4: DataServer Best Practices Revised & Revisited Noel Shannon Senior Solution Consultant."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

B4: DataServer Best Practices Revised & Revisited Noel Shannon Senior Solution Consultant.

Similar presentations

Presentation on theme: "B4: DataServer Best Practices Revised & Revisited Noel Shannon Senior Solution Consultant."— Presentation transcript:

Similar presentations

About project

Feedback