Содержание
- 2. Objective By the end of this module, you’ll be able to— Identify best practices and guidelines
- 3. Module Topics Database Structures Best Practices – Runtime Performance Database Access Commands Best Practices – Read
- 4. Introduction The module discusses best practices and guidelines to achieve better performance for both AB Suite
- 5. Database Structures
- 6. Database Structures—Windows Runtime A SQL Server database table is created for each persistent class. Persistent attribute
- 7. Database Structures—MCP Runtime A DMS II dataset is created for each class containing persistent attributes. A
- 8. Database Structures—MCP Runtime All Profiles (sets or Subsets) are INDEX SEQUENTIAL. The DMS II database schema
- 9. Multiple Event Sets Multiple event sets allow unrelated transactions to be split into multiple event sets.
- 10. Persistent Structures Persistent structures are created as a table in the database. For example, an ispec
- 11. Polymorphic Persistent Structures When a persistent class inherits from a superclass, the database table acts as
- 12. Better Runtime Performance: Best Practices
- 13. Minimizing Deadlocks and Performance Degradation Minimizing Deadlocks: For event or persistent inheritance structures, consider applying sections.
- 14. Minimizing Deadlocks and Performance Degradation Excessive use of the integrity settings can result in deadlocks and
- 15. Minimizing Deadlocks and Performance Degradation For example, an application might have a control class (CNTRL) that
- 16. Minimizing Deadlocks and Performance Degradation For AB Suite applications, a valid restart point/syncpoint is created for
- 17. Minimizing Deadlocks and Performance Degradation When heavy processing is done while the ispec or report is
- 18. Minimizing Deadlocks and Performance Degradation For profiles where Duplicates Allowed property is set to True and
- 19. Minimizing Deadlocks and Performance Degradation For very high activity datasets, where Extended Edition segment configuration property
- 20. Minimizing Deadlocks and Performance Degradation The KEYONLY command option increases the efficiency of LU and DT
- 21. Minimizing Deadlocks and Performance Degradation The KEYONLY command option, when used with the Determine commands, retrieves
- 22. Minimizing Deadlocks and Performance Degradation You can add profile data elements using the profile’s Data tab.
- 23. Guidelines for Optimum Transaction Throughput You can use the following guidelines for optimum transaction throughput on
- 24. Guidelines for Optimum Transaction Throughput Database Structure Sectioning - Identifying candidates Enable LOCKSTATISTICS via the Visible
- 25. Guidelines for Optimum Transaction Throughput Database Options/Settings Set the Extended Edition property to True. Set REAPPLYCOMPLETED/INDEPENDENTTRANS
- 26. Guidelines for Optimum Transaction Throughput COMS Settings Set the Global “Input Queue Allowedcore” to a large
- 27. Using SLEEP and CRITICAL POINT Using SLEEP and CRITICAL POINT (CP) Reports should be structured to
- 28. Performance Optimization in Windows The default technique used by AB Suite Windows Runtime to read records
- 29. Using DataReader Using DataReader, records are retrieved into an internal memory cache with many records being
- 30. Using DataReader By default the DataReader Capable configuration property is set to True. Windows
- 31. Using DataReader DataReader can cause some Determine command behavior differences compared to Cursors. The following table
- 32. Using DataReader Apart from setting the DataReader Capable configuration property, it is possible to enable or
- 33. Using DataReader Configure with XML file An XML configuration file called DBConfig.xml can be used to
- 34. Using MULTI Behavior The MULTI setting can be defined within a configuration file called DBConfig.xml. Different
- 35. Using MULTI Behavior With MULTI defined, when a read loop is first entered, a block containing
- 36. Setting Transaction Isolation Level Transaction Isolation Level is a COM+ component setting that indicates how records
- 37. Setting Transaction Isolation Level The Transaction Isolation Level setting can be defined within a configuration file
- 38. Using Non-Phased SQL During the execution of various Determine commands using multi-key profiles, SQL SELECT statements
- 39. Using Non-Phased SQL The following table summarizes the difference between the Phased SQL and Non-Phased SQL:
- 40. Using Non-Phased SQL The Phased SQL setting can be defined within a configuration file called DBConfig.xml.
- 41. Using Non-Phased SQL Why use Non-Phased SQL? To reduce the number round trips to SQL Server
- 42. Database Access Commands
- 43. Profile Structures Analyse the profiles defined in your model. More profiles result in additional database updates
- 44. Best Practices – Read and Write Operations Avoid excessive reads and writes Use a Group clause
- 45. Best Practices – Read and Write Operations As you read a record into multiple instances of
- 46. Best Practices – Read and Write Operations Use instances of a class definition represented by an
- 47. Best Practices – Read and Write Operations You can use the ForEach Polymorphic database command to
- 48. Best Practices – Read and Write Operations
- 50. Скачать презентацию