Guideline for Software Developer - How to write DBA-friendly Software

Introduction

This article is intended to collect best practise information from various sources in order to become the one-stop place for Software Organisations buidling RDBMS based software products, if they intend to be DBA friendly. This is not yet another tuning guide. Therefore it deals less with statement tuning, but more about the aspects of instalaltion and maintenance. Especially listing unhelpfull instalaltion requirements and procedures.

Work in progress...

I kicked off this article after finding no real comprehensive checklists and asking on Oracle Mix.

Planning and Sizing

In order to allow the DBA proper pre-installation planning, the following characteristics of the software to be installed should be known:

• Number and Details of used Schema
• Space usage of Tables, Index and LOBs as well as undo
• Number of Transactions (commits) on average and peak
• change volume (affects redolog size and archive storage)
• Character Set supported vor normal and national VARCHAR
• Options required (Partitions, Function based Index, JVM, ...)
• Storage Parameters for various Tablespaces (Blocksize, SSM, ...)
• Suported Compatibility Versions, Software Versions and required Patches
• Support for RAC, can use Slaves or Standby Database?
  
• Service Definitions
• Number and Load Distribution of Connections (Session, Process, Pool/Shared/Dispatcher)
• User Authorisation (User Logins, Proxy Users, External Authentication, Application Server Users)
• Auditing Requirements
  
• ...
  

Links

In this section you find links to related web pages.

• Oracle Mix - ISV Group
•