Establishing Enterprise Data Standards - High-Performance Web Databases: Design, Development, and Deployment - page 15

Exhibit 2-3. Architecture and physical environment category.

Subcategory Comments

Data Partitioning Position nonvolatile data near the client platforms that access it.

Physical Architecture Data architecture for development, testing, and production.

Data Access Call stored procedures from client platforms to update database

table data.
Use views to select information from database tables.
Return minimum number of data rows to the client.

Locking Assume optimistic locking approach instead of the pessimistic.

PROCESS FOR DEFINING ENTERPRISE DATA STANDARDS

There are many approaches for defining enterprise data standards.
Project experience has shown that the best approach for meeting the
objectives identified earlier in this article is the early adoption of a simpli-
fied set of enterprise data standards that are easily understood and used
across the organization. This is best achieved by starting with a set of
proven standards from previous projects or from external vendors. For
example, companies such as Microsoft, Forte, and Sybase all have publica-
tions that define standards to one degree or another. These can be readily
found by searching the Websites of the vendors or phoning their marketing
or technical departments. Exhibit 7 shows a high level view of a process
that should be completed in your organization to define Enterprise Data
Standards. This process has been defined through experiences on many
small to large projects, and based on observations about what worked well
and what did not work so well on the projects.

As shown in Exhibit 7, the “Borrow Approach” is the simplest to define
or implement, which involves borrowing data standards from vendors,
other successful projects, or organizations such as the American National
Standards Institute (ANSI) or International Standards Organization (ISO)
that define industry standards. A more complete list of organizations that
define standards is provided at the end of this article. Such standards can

Exhibit 2-4. Procedures category.

Subcategory Comments

Change Management Standards All database objects should be created with SQL

Scripts. The scripts should be saved in tools such as
Microsoft SourceSave.

System Management Standards New client platforms will be configured using

Microsoft SMS with local data tables for static data
values.

Version Control Standards Check in/Check out, delta management.