Database Reference
In-Depth Information
Testing revisions. Revisions are tested through test versions of application pro-
grams. Have queries ready to view data changes in the database. Ensure that ref-
erential integrity and other constraints are not violated.
Revisions promoted to production. When test versions of application programs are
promoted to production, the corresponding schema revisions must also be moved
to the production environment. Have a good approval procedure for the move to
production. For major revisions involving creation of new tables, you will be
required to populate the new tables with initial data.
Fallback procedure. When you promote test versions of application enhancements
and the corresponding schema revisions to production, if you run into unforeseen
problems after the move to production, have a fallback procedure to revert to the
previous state of the schema. However extensive testing could have been, there is
always a slight chance of revisions not working properly; safeguard against such
mishaps with a good fallback procedure.
DBMS Version Upgrades
From time to time, your database vendor will announce upgrades to the DBMS.
Some of these newer versions contain fixes to problems noticed in the earlier
versions. Most of the newer versions provide enhancements and better ways of
managing the database versions. Many of the recent upgrades to relational DBMS
focus on the merging of database and Internet technologies. Whether or not
enhancements in the upgraded versions are directly beneficial to your environment,
eventually you will be forced to move up to the latest version. Vendors usually
discontinue supporting older versions of DBMSs after a designated period.
Version upgrades cause potentially serious interruption to the normal work
unless they are properly managed. Good planning minimizes the disruption.
Vendors try to pressure their customers into upgrades on their schedules based on
their new releases. If the timing is not convenient for you, resist the initiatives from
the vendor. Schedule the upgrade at your convenience and based on when your
users can tolerate interruption.
The DBA takes primary responsibility in installing DBMS version upgrades. But
others from the database and application project teams as well as user representa-
tives assist with the testing. Here is a brief list of major tasks associated with DBMS
version upgrades:
Coordinate with vendor for assistance during the upgrade process
Ensure that new version is fully tested by the vendor and free from any errors
Prepare test database system to install new version
Configure the new version with proper initialization parameters
Revise database start-up job, if necessary
Create a test plan and review the plan with other team members and users
Compile list of programs to be tested with test conditions and assign responsi-
bilities for testing
Verify and approve test results
Search WWH ::




Custom Search