You are on page 1of 8

CC6 Reviewer Chap.

5-7
Structured Query - is composed of commands that enable users to create database and table
Language (SQL) structures, perform various types of data manipulation and data administration, and
query the database to extract useful information.
- focuses on data definition (creating tables and indexes) and data manipulation
(adding, modifying, deleting, and retrieving data).
Database - allows you to create database and table structures, perform basic data
Language management chores (add, delete, and modify), and perform complex queries
designed to transform the raw data into useful information
data - it includes commands to insert, update, delete, and retrieve data within the
manipulation database tables.
language (DML)
data definition - it includes commands to create database objects such as tables, indexes, and
language (DDL) views, as well as commands to define access rights to those database objects.
transaction - commands in SQL are executed within the context of a transaction, which is a
control language logical unit of work composed of one or more SQL statements, as defined by
(TCL) business rules (see Chapter 10, Transaction Management and Concurrency Control).
data control - Data control commands are used to control access to data objects, such as giving a
language (DCL). one user permission to only view the PRODUCT table, and giving another use
permission to change the data in the PRODUCT table.
data type - is a specification about the kinds of data that can be stored in an attribute.
American - prescribes a standard SQL
National
Standards
Institute (ANSI)
Character data - is composed of any printable characters such as alphabetic values, digits,
punctuation, and special characters.
- is also often referred to as a “string” because it is a collection of characters
threaded together to create the value
Numeric data - is composed of digits, such that the data has a specific numeric value.
Date data - is composed of date and, occasionally, time values.
SELECT - specifies the attributes to be returned by the query
- columnlist
-*
FROM - specifies the table(s) from which the data will be retrieved
- tablelist
- PRODUCT;
WHERE - filters the rows of data based on provided criteria
GROUP BY - groups the rows of data into collections based on sharing the same values in one
or more attributes
HAVING - filters the groups formed in the GROUP BY clause based on provided criteria
ORDER BY - sorts the final query result rows in ascending or descending order based on the
values of one or more attributes.
column list - allows the programmer to specify which columns should be
returned, as shown in the next query
Column Aliases - Recall that the attribute within an entity is implemented as a column in the table.

Computed - (also called a calculated column) represents a derived attribute, as discussed in


Columns Chapter 4, Entity Relationship Modeling.
Date Arithmetic - Date data in the column list can be interesting when used in computed fields.
Internally, the DBMS stores a date value in a numeric format.
Outer Joins -returns not only the rows matching the join condition but it also returns the rows
with unmatched values.
Right outer join -returns not only the rows matching the join condition , but its also return the rows
in the right table with unmatched values in the left table.
Cross Join -performs a relational product (also known as the Cartesian product) of two tables.
Joining Tables -An alias may be used to identify the source table from which the data is taken.
with an Alias
Recursive Joins -a table alias is especially useful when a table must be joined to itself in a recursive
query, as is the case when working with unary relationships.
Order by Clause -the order by clause is especially useful when the listing order is important to you.
Options/ Order -is useful in many application , especially because the DESC qualifier can be invoked.
By Clause
String Functions -String manipulation are among the most-used functions in programming.

C.R.Gomez WMA-3C
CC6 Reviewer Chap.5-7
Numeric --can be grouped in many different ways such as algebraic, trigonometric and
functions logarithmic.
Date and Time -all date functions take one parameter of a date or character data type and return
Functions value.
All SQL -standard DBMS support date and time functions.
SQL Functions -the data in database is the basis of critical business information.
-Generating information from data often requires many data manipulations.
Correlated -is a subquery that executes once for each row in the outer query.
Subqueries
Attribute List -can also include a subquery expression, also known as an inline subquery.
Subqueries/
Attribute List
Where -the most common type of subquery uses an inner select subquery on the right side
Subqueries of a where comparison expression.
Subquery -is a query inside another query.
-is normally expressed inside parenthesis.
First query in the --is known as the outer query,
SQL statement
The query inside -is known theinner query.
the SQL
statement
Inner query -executed first.
Output of an -is used as the input for the outer query.
inner query
Entire SQL -is sometimes referred to as nested query.
statement
Boolean Algebra -is dedicated to the use of logical operators.
Logical operator -is used to negate the result of a conditional expression.
NOT
Logical operator -has the same SQL syntax requirement as OR.
AND
Comparison -date procedures are often more software-specific than the other SQL procedures.
Operators on
Dates
Selecting Rows -you can select partial table contents by placing restriction on the rows to be
with Conditional included in the output.
Restrictions
ANSI-standard -allows the use of special operator in conjunction with the WHERE clause.
SQL
Data Architecture -it is first data management function that interacts with and is influenced by the
Management governance function.
-Is the process of defining and maintaining specifications.
Data architecture -is most valuable when it supports the information needs of the entire enterprises.
Enterprise data -is part of the larger enterprises architecture ,where data architecture integrates
architecture with other business and technology architecture.
-is an integrated set of specification and documents.
-is an important part of the larger enterprise architecture that includes process,
business, systems and technology architecture.
Enterprise Data -the heart and soul of enterprises data architecture.
model
Information value -aligns data with business processes and other enterprises architecture
chain analysis components.
Architecture -is an organized arrangement of component elements, which optimize the function,
performance, feasibility, cost and/or aesthetic of the overall structure or system.
-is an integrated set of business and IT specification models and artifacts reflecting
enterprises integration and standardization requirements.
Enterprise -provides a systematic approach to managing information and systems assets,
Architecture addressing strategic business requirements and enabling informed portfolio
management of the organization projects.
Enterprise  Information Architecture
architecture  Process Architecture
includes many  Business architecture
related models  Systems Architecture

C.R.Gomez WMA-3C
CC6 Reviewer Chap.5-7
and artifacts  Technology Architecture
 Information value chain analysis artifacts
Architectural -provide a way of thinking about and understanding architecture and the structures
Framework or systems requiring architecture.
Classification -organize the structures and views that encompass enterprise architecture.
Frameworks
Process -specify methods for business and systems planning, analysis and design processes
Frameworks
The Open Group -is a process framework and standard software development lifecycle (SDLC)
Architectural method by the open group , a vendor and technology neutral consortium for
Framework defining and promoting open standards for global interoperability.
(TOGAF)
Zachman -is the most widely known and adopted architectural framework.
Enterprise
Framework
Planner -list of business elements defining scope identified by Strategies as theorist.
Perspective -a list of subject areas and business entities.
(Scope Contexts)
Owner -semantic models of the business relationships between business elements defined
Perspective by Executive Leaders as owners.
(Business -conceptual data models showing the relationships between entities.
Concepts)
Designer -logical models detailing system requirements and unconstrained design
Perspective represented by Architects as designers.
(System Logic) -Fully attributed and normalized logical data model.
Builder -physical models optimizing the design for implementation for specific use under
Perspective the constraints of specific technology, people, cost, and time frames specified by
(Technology Engineers as Builders.
Physics) -optimized for constraining technology.
Implementer -a technology specific, out of context view of how components are assemble and
Perspective operate configured by technician implementers.
(Components -detailed representations of data structures, typically in SQL.
Assembles)
Participants -actual functioning system instances used by workers as participants.
Perspective
(Operation
Classes)
Functioning -actual implemented instances.
Enterprise
Zachman -enables concentration on selected cells without losing sight of the “Big Picture”.
Framework
Business Entities -are classes of real business things and concepts.
-are the primary organizational structures in a conceptual data model.
Data model -is a set of data specification and related diagrams that reflect data requirements
and designs.
Integrated -means that all of the data and rules in an organization are depicted once, and fit
together seamlessly.
Subject-oriented -means the model is divided onto commonly recognized subject areas that span
across multiple business processes and application systems.
Essentials -means the data critical to the effective operation and decisions making of the
organization.
Enterprise data -is an integrated set of closely related deliverables.
model -is a significant investment in defining and documenting an organization’s
vocabulary, business rules and business knowledge.
Enterprise data -is the set of conceptual data model diagrams for each subject area.
model

Technology  Current – products currently supported and used.


architecture  Deployment Period-products deployed for use in the next 1-2 years.
components  Strategic Period- product expected to be available for use in the next 2+
years.
 Retirement-products the organization has retired or intends to retire this

C.R.Gomez WMA-3C
CC6 Reviewer Chap.5-7
year.
 Preferred-products preferred for use by most application.
 Containment-products limited to use by certain application.
 Emerging-products being researched and piloted for possible future
deployment.
Data warehouse -focuses on how data changes and snapshots are stored in data warehouse systems
architecture for maximum usefulness and performance.
Taxonomy -is the hierarchical structure used for outlining topics.
Data Governance -is defined as the exercise of authority and control (planning, monitoring, and
enforcement) over the management of data asset.
Strategy -defining, communicating and driving execution of data strategy and data
governance strategy.
Policy -setting and enforcing policies related to data and metadata management, access,
usage, security and quality.
Standard and -setting and enforcing data quality and data architecture standard.
quality
Oversight -providing hands-on observation, audit and correction in keys areas of quality,
policy and data management.
Compliance -ensuring the organization can meet data-related regulatory compliance
requirements.
Issue -identifying ,defining ,escalating and resolving issues related to data security, data
management access, data quality, regulatory compliance, data ownership, policy, standards,
terminology or data governance procedure.
Data -sponsoring efforts to improve data management practices.
management
projects
Data asset -setting standards and processes to consistently define the business value of data
valuation assets.
Business Driver -the most common driver for data governance is often regulatory compliance,
especially for heavily regulated industries such as financial services and healthcare.
General risk -oversight of the risks data poses to finance or reputation, including response to
management legal and regulatory issues.
Data security -protection of data assets through controls for the availability, usability, integrity,
consistency, auditability and security of data.
Privacy -control of private confidential Personal information (PII) through policy and
compliance monitoring.
Regulatory -the ability to respond efficiently and consistently to regulatory requirements
compliance --the CDO is not directly understands and works within required local, national and
international regulatory environments and how these impact the organization and
their management activities
Data quality -the ability to contribute to improved business performance by making data more
improvement reliable.
Metadata -establishment of a business glossary to define and locate data in the organization.
Management -ensuring the wide range of other metadata is managed and made available to the
organization.
Efficiency in -improvements to address issues and opportunities in data management across the
development organization including management of data specific technical debt through
projects governance of the data lifecycle.
Vendor -control of contracts dealing with data such as cloud storage, external data
Management purchase , sales of data as a product and outsourcing data operations.
Goal of data -is to enable an organization to manage data as an asset.
governance
Sustainable -it is an ongoing process that requires organizational commitment.
Embedded - data governance is not an ad-on process.
- data governance activities need to be incorporated into development methods for
software, use of data for analytics, management of master data and risk
management.
Measured - data governance done well positive financial impact, but demonstrating this
impact requires understanding the starting point and planning for measurable
improvement.
Leadership and -Successful data governance starts with visionary and committed leadership.
Strategy

C.R.Gomez WMA-3C
CC6 Reviewer Chap.5-7
Business Driven - data governance is a business program and as such must govern it decision related
to data as much as it governs business interaction.
Shared -across all data management knowledge areas, data governance is a shared
responsibility responsibility between business data stewards and technical data management
professional.
Multi-layered - data governance occurs at both the enterprise and local levels and often at levels
in between.
Framework- - data governance must establish an operating framework that defines
based accountabilities and interactions.
Principle-based -Guiding principles are the foundation of data governance activities and especially
of data governance policy.
Data Stewardship -is the most common label to describe accountability and responsibility for data and
processes that ensure effective control and use of data assets.
Stewards -is a person whose job it is to manage the property of another person.
Impact of -highly regulated organizations will have a different mindset and operating model of
regulation data governance than those less regulated.
Cultural Factors - governance strategy will need to advocate for an operating model that fits with
organizational culture, while still progressing change.
Business Model -links with specific IT strategy ,data architecture and application integration function
should be reflected in the target operation framework design.
Value of data to -organizations that use data as a crucial commodity will need an operating model
the organization that reflects the role of data.
Charter -Identifies the business driver, vision, mission and principles for data governance
including readiness assessment, internal process discovery and current issues or
success criteria.

Operating -defines structure and responsibility for data governance activities.


framework and
accountabilities
Implementation -timeframes for the roll out of policies and directions and directives, business
roadmap glossary, architecture, asset valuation, standards and procedures, expected changes
to business and technology processes and deliverables to support auditing activities
and compliance.
Plan for -describing a target state of sustainable data governance activities.
operational
success
Data governance -defines the scope and approach to governance efforts.
strategy
SDLC/developme - data governance program identifies control points where enterprise policies,
nt framework processes and standards can be developed in the system or application
development life cycles.
Budget and -the CDO is not directly in control of all data acquisition related budgets, then the
Funding office can be a focal point for preventing duplicate efforts and ensuring optimization
of acquired data assets.
Procurement and -the CDO works with vendor/partner management or procurement to develop and
Contracts enforce standard contract language vis-à-vis data management contracts,
Data quality -is a part of discovery.
analysis
Business -assessment examines how well the organization aligns uses of data with business
alignment strategy
Collaborative -this assessment characterizes the organizations ability to collaborative in the
readiness management and use of data.
Capacity to -it is important to measure the capacity for the organization to change behaviors
change required for adapting data governance.
Data -understand what the organization does with data, measures its current data
management management capabilities and capacity.
maturity
Perform -that describe the current state of an organizations information management
readiness capabilities, maturity and effectiveness are crucial to planning a data governance
Assessment program.
Coordinating -lead and represent teams of business and technical data stewards in discussion
data stewards across terms and with executive data stewards.

C.R.Gomez WMA-3C
CC6 Reviewer Chap.5-7
Technical data -are IT professionals operating within one of the knowledge areas such as data
stewards integration, database administrators, business intelligence specialist data quality
analysts or metadata administrators.
A data owner -is a business data steward, who has approval authority for decisions about data
within their domain.
Business Data -are business professional, most often recognized subject matter experts,
stewards accountable for a subset of data.
Enterprise Data -have oversight of a data domain across business functions
stewards
Executive Data -are senior manager who serve on a data governance council.
stewards
Chief Data -may chair data governance bodies in lieu of the CDO or may act as a CDO in a
stewards virtual or distribute data governance organization.
Risk cost -a valuation based on potential penalties, remediation and litigation expenses.
Selling data -some organization package data as a product or sell insights gained from their data,
Identified -the value of income can be gained from opportunities identified in the data.
opportunities
Market Value -the value as a business asset at the time of a merger or acquisition.
Replacement cost -it is lost in a disaster or data breach including the transactions, domains, catalogs,
documents and metrics within an organization.
Data asset -is the process of understanding and calculating the economic value of data to an
valuation organization.
Data policies -directives that codify principles and management intent into fundamental rules
governing the creation, acquisition , integrity, security, quality and use of data and
information.

C.R.Gomez WMA-3C
CC6 Reviewer Chap.5-7

C.R.Gomez WMA-3C
CC6 Reviewer Chap.5-7

Good Luck and


advanced
Merry
Christmas
everyone .

C.R.Gomez WMA-3C

You might also like