In this report, you will discover:
- Why spreadsheets are working against you and de-motivating your team
- A spreadsheet “health diagnosis” checklist
- How incentive plans can drive behavior with better accuracy and objectivity
This paper is an overview of the issues that arise from implementing object persistence with a relational database. The basis for this paper is our recent experience with Object-Oriented projects that used relational database technology.
There is often a great deal of confusion in determining whether an object database management system (ODBMS) is right for you. Most of this confusion can be resolved by focusing on your application's requirements. In those situations where the application requires the very clear advantages of an ODBMS, choosing which ODBMS becomes a continuation of the exercise of analyzing those application requirements.
As business users expand to newer types of applications, and grow older ones, their attempts to use RDBMS encounter the "Relational Wall," where RDBMS technology no longer provides the performance and functionality needed. This paper measures the wall, explains what model and architectural differences cause it, how to foresee it, and how to avoid it.