Chapter 4- Front Room Flashcards

1
Q

Front Room

A

-Public face of the warehouse
-Day-to-day aspect that business users work with
-Goal is to make information accessible as possible

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Access Tool Data Stores

A

-Data becomes more available and closer to the users in a diffused form
-Ability to create ad-hoc reports
-Data exported to Excel for further analysis
-cached data allows for quicker response

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Standard Reporting Data Stores

A

-multiple data marts may be used to draw the reports

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

personal data marts

A

-idea has been embraced long ago
-may require replication framework to ensure they are always in sync

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Disposable Data Marts

A

-set of data create to support a short-lived business situation
-allows data be designed for specifically event
-Allows business rules and filters to create simple sandbox for analysts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Application Models

A

-Data Mining
-collection of powerful analysis techniques for making sense out of large data sets

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Downstream Systems

A

-Reporting close to operational side
-Transaction oriented

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

5 types of activities for differing granularity and allocating

A

-Warehouse or Metadata Browsing
-Access and Security
-Activity Monitoring
-Query Management
-Standard Reporting

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Warehouse or Metadata Browsing

A

-Metadata subsets of the database to simplify user’s view
-Takes work to initiate but will be rewarded with self-sufficient user community
-Allows browsing database through descriptions or metadata

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Access Security

A

-Facilitates a user’s connection to the database
-User’s access and security rely on authorization and authentication
-possible require physical evidence of identity like magnetic cards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Activity Monitoring

A

Captures info about the use of the DW

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is Activity Monitoring Centered around?

A

Performance
User support
Marketing
Planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Activity Monitoring: Performance

A

Usage
Shows which table and columns are most joined, selected, aggregated or filtered

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Activity Monitoring: User Support

A

-Monitors to see if trained users have success
-Understand what users are doing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Activity Monitoring: marketing

A

-Outputs Statistics
-Able to see curve, whether growth, flat or decreasing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Activity Monitoring: Planning

A

-Quantifies the need and time for capacity increases through monitoring of usage, query time

17
Q

Query Management

A
  • capabilities that manage exchange between query formulation, execution and return of results
18
Q

Query Management: Content simplification

A

Shields user from complex queries
-may include limiting user’s view to subsets of tables
-usually hidden in front end

19
Q

Query Management: Query reformulation

A

-queries are parsed and reformulated for best solution

20
Q

query Management: Query retargeting and Multipass SQL

A
  • Looks up elements in metadata and redirects query to appropriate location
    -includes simple redirects, heterogeneous joins and other functions such as unions and minus
21
Q

Query Management: Date Awareness

A

-Allows user to ask for items like current year to date
-periods dimension would assist in identifying appropriate dates

22
Q

query Management: Query Governing

A

-Limiting run times of queries or # of rows

23
Q

Query Service Location 3 major options

A

-Desktop
-App Server
-Database

24
Q

Query Service Locations: Database Advantage

A

all front end tools can take advantage of services on the database

25
Query Service Locations: Database disadvantage
more limiting than application server because it is not supported across machines and DB
26
Requirements for standard Reporting Tools
-Report development environment -Report execution server -Parameter or variable driven capabilities -Time and event-based scheduling of report execution
27
Future access Services : Authentication and authorization
-Identify user and grant access -Security mechanism to see what permission a user has
28
Future access Services :Centralized services
access services on app server or DB. to centralize data
29
Future access Services :Vendor consolidation
- ability to seamlessly flow despite the vendors -
30
Future access Services : Web-based customer access
-Direct access to share info with customers -ability to share monthly summaries with customers -Info can be sliced in different ways
31
4 main data access categories include:
- push-button -standard reports -ad Hoc -data mining
32
Web Implications for data access
-requirements for DW and architectureal implications -Architecture should have access services for web server supporting DB
33
Ways Web is impacting the data access tools
-Platform independent -Zero maintenance -Low cost
34
Desktop Tool Architecture Approaches
-Direct Connect ( Two Tier) -ROLAP App Layer ( 3 Tier) -MOLAP App Layer (3+ Tier)
35
Direct Connect
- Desktop tool to connect directly to database - query management not required
36
Direct Connect Advantages
-Easy to install and administer -Relatively simple to manage
37
Direct Connect Disadvantages:
- Does not scale well Simple -Sparser metadata -limited functionality
38
ROLAP
-App layer is loacted between DB and Front Ent -allows less footprints on desktop -Presents DB as multidimensional environment -uses metadata
39
MOLAP
-Between relational data warehouse and Front end -middle tier called multidimensional DB cube