Getting Started with IBM Data Studio for DB2

Chapter 10 – Developing data web services 315
Develop -- Code, generate, test, tune, and package data access layers, database
routines, and data services. This step is where the data access application is built. The
data access may be part of a larger application development process, so it’s important
to collaborate closely with business developers and to ensure that application
requirement changes are reflected back to the data architect or database administrator
for changes. In addition, developers may be responsible for ensuring that the data
access they create (SQL, XQuery, Java, data web services, etc.) not only returns the
correct result but also performs efficiently. Use of representative test data and test
databases is often used. Because of regulations around how personally identifiable
information such as social security numbers and credit card numbers can be handled,
it’s critical that developers who need test data are compliant with those regulations
while still having representative test data.
Deploy -- Install, configure, change, and promote applications, services, and
databases into production. This phase includes a well-planned strategy for migrating
databases (or database schema changes), data and applications into production. The
goal is to do this as swiftly as possible and with the least amount of disruption to
existing applications and databases to avoid affecting other applications and to do it
without error. Deployment can also mean deploying changes.
Operate -- Administer databases to meet service level agreements and security
requirements while providing responsive service to emergent issues. This phase of the
lifecycle is the bread and butter of a typical database administrator’s day. They
authorize (or remove authorizations) for data access. They not only have to prepare for
possible failures by ensuring timely backups, but they must also ensure that the
database is performing well and they must be able to respond to issues as they arise.
Because many failures can be difficult to isolate (that is, is a failure occurring in the
database, the application server, the network, the hardware?), it’s critical that all
members of the IT staff have information to help them isolate the problem as quickly as
possible so that the right person can fix the problem, whether it’s the database
administrator, the network administrator, the application administrator or someone else.
Optimize -- Provide pro-active planning and optimization for applications and
workloads including trend analysis, capacity and growth planning, and application
retirement including executing strategies to meet future requirements. This phase is
where database administrators can really bring value to the business. It may take a
backseat to the constant interrupt-driven needs of day to day operations, but it is a
critical phase to ensure that costs are kept down and performance remains acceptable
as the business grows and as more applications drive more users against the
databases. It’s critical that performance trends and data growth trends are analyzed
and accommodated. A strategy for archiving old data is required for two reasons: 1) to
manage data growth to ensure performance is not adversely affected and 2) to comply
with regulations for data retention.
Govern -- Establish, communicate, run, and audit policies and practices to
standardize, protect and retain data in compliance with government, industry, or
organizational requirements and regulations. Not limited to a single phase, governance