Progress RDBMS® is an open, flexible, scalable, and highly available database solution that supports virtually unlimited numbers of users and transactions with minimal administration and maintenance. Although dealing with the RDBMS is mostly a development task, this powerful database engine deserves its own section.



Content Index

English Smart Progress Database Maintenance

SmartDBcheck is a DBA assistant making administration of Progress databases easier. It collects data associated with storage objects from different sources including the VST, presenting all properties 'ready to manage' in a simple user interface. SmartDBcheck provides a few pretty smart methods to deal with potential performance issues and V9 storage areas.

English Smart Progress® Database Design

This article provides an overview of the most important steps on Progress® database design. Starting at the white board discussing well tried naming conventions, the implementation of relations without improper usage of attributes with business meaning up to smart P4GL coding practice this guide covers a wide range of design issues and should help gaining a clean database design.


OffSite Links

English Behind the Scenes - Blocks, Bytes & Disk Space

A short guide to understanding and optimizing block size both for performance and best usage of disk space (Progress® version 9 and prior).

English Some Surprising Benefits of Using Storage Areas

Tom Bascom's fine article on storage areas describes the benefits of proper implementation of storage areas in the view of a real life case study. Progress storage areas are usually viewed as an administrative tool rather than as a means for directly improving performance. Faster and more selective index rebuild and dump/load, the ability to easily drop "temp areas", running dbanalys much more quickly and other benefits are all great reasons to use storage areas. Less well known is that many of the same factors that enable improved manageability also impact performance in interesting ways.

English Why You Need The Before-image Log

"The before-image log, also called the 'bi file', contains the primary transaction log of the Progress RDBMS. It is an integral and essential part of every database and is just as important as the data extents used to store table data and their associated indexes. Without the before-image log extents, the database cannot be accessed." ... "Although it is called the 'before-image' log, the data stored in it are not before-images of anything. The name is historical and perhaps was poorly chosen. The before-image log contains records, called 'notes', that allow previously made changes to the database to be repeated (redone) or rolled back (undone). The before-image log is mainly used for two things: to perform crash recovery in the event of a failure, and to perform transaction rollback during normal processing." This long and very detailed post by Gus Bjorklund is a must-read for every Progress® DBA out there.

English Progress® Metadata

The "Engine Crew Monograph No. 14" (or 17?) by Gus Bjorklund explains the Progress® meta data. The article was written in 1998, but along with a few other sources and Dan Foreman's book on VST you'll get the current picture.

English The Progress® Transaction 'Leak'

One of the great characteristics of the Progress® RDBMS is a feature called transaction integrity. Properly employed, it guarantees that a collection of record updates is either committed in its entirety to the database or completely rolled back. This provides application programmers an excellent means of encapsulating changes, and relieves them of the effort of writing data-nursing routines to clean up the nasty messes left over from programs that trip over unexpected conditions that would otherwise contaminate the data. But in the real world where programmers are fallible and perhaps even unaware, it is very easy to write a procedure in which the transaction can 'leak' by rolling back some database changes while committing others. This great article by David Takle sheds some light on the 'Progress® Transaction Leak' phenomenon. Local .doc

English Progress v9.1c for UNIX®: Integrating with a NetApp® Filer

This document describes the steps necessary to integrate Progress v9.1c for UNIX with a Network Appliance filer. Specifically, it covers the following issues:
· Preparation of both the UNIX server and the NetApp filer for the Progress installation
· Installation of Progress on a UNIX server in a NetApp filer environment
· Creation of Progress database extents on a filer
· Creation of Progress BI (before image) files on a filer
· Creation of Progress AI (after image) files on a filer
· Migration of existing Progress files (i.e. database extents, BI, AI, event log, and transaction log files) from local disk onto a filer

· Home

· Progress

· RDBMS

· Smart DBA

· Smart Design

· Block Sizes

· StorageAreas

· The BI File

· Metadata

· Transaction Leak

· NetApp Filer

· Web Links

· Link to us

· Contact

· What's new

· Site map

· Get Help


Most popular:

· Site Feeds

· Database Design Guide

· Google Sitemaps

· smartDataPump

· Spider Support

· How To Link Properly


Free Tools:

· Sitemap Validator

· Simple Sitemaps

· Spider Spoofer

· Ad & Click Tracking



Search Google
Web Site

Add to My Yahoo!
Syndicate our Content via RSS FeedSyndicate our Content via RSS Feed



To eliminate unwanted email from ALL sources use SpamArrest!






Digg this · Add to del.icio.us · Add to Furl · We Can Help You!




Home · Categories · Articles & Tutorials · Syndicated News, Blogs & Knowledge Bases · Web Log Archives


Top of page

No Ads


Copyright © 2004, 2005 by Smart IT Consulting · Reprinting except quotes along with a link to this site is prohibited · Contact · Privacy