35

Objectives:
In this presentation we are going to talk about main purpose for implementing DW – decision support system. Also descusion will take point in explaining pre(post) implemntation problems, growing demands and ways how they were solved. Furthermore presentation will cover overviewof ZABA DW architecture and improvements gained from implementing BI technology in Zagrebacka bank.

Outline:
Introduction
Environment
Problems
System architecture
Gains and improvements

Full Abstract:
Lack of information? Your competition understands their client needs better then you do? Don’t have clear picture of your expenses? This are some questions for witch BI technology must provide answer. In financial industry time is critical, if you don’t provide exactly what client need, someone else will. Distributing information at the right time to the right people in right format is essential for decision making. This is one of the main reason to start implementing BI technologies. In order to do that you have to centralize your data (DW) and work on data quality 24/7. In our paper we will clarify ZABA’s data environment on which DW was build (implementation problems, platform, software, organization etc....), implemented mechanisms that help us to improve ETL processes and DW monitoring, including gains and improvements review. In the end we will discuss about our future layout for developing our BI processes.

Objectives:
Provide some recomendations how to achieve higher level of success in the projects of BI solutions and DW development.

Outline:
Traditional and modern DW development
Business and organisational issues
Multiple applications and multiple DB sources complexity
Data quality, data cleansing and consolidation
Design layer architecture
Some recomendations for the usage of design layer architecture in the BI solution development process

Full Abstract:
Multiple data sources, need for reliable and timely reporting and growing business requirements for ad-hoc reporting are most often the reason why companies start DW and BI projects. DW modeling methodologies and OLAP based BI solutions are nowadays widely used by a number of companies. However, due to poor data quality, redundancy, inconsistency and complexity of transactional data, business needs are often not met. On the other hand, faster changes in business environment lead to ever higher business expectations.
This presentation will start with an overwiew of basic principles of developing traditional as well as modern DW solutions. It will then continue with some typical issues  that we have been meeting during our consultancy on DW development projects.
Besides organisational and business issues, application systems complexity and inconsistent business terminology are major underlying reasons for most of the problems. The last part of the  presentation will include recomendations how to resolve some of the most critical problems regarding the usage of design layer modelling architecture. Design layer architecure will be outlined as the method for simplification, better understanding and  easier control of the whole DW and BI solution development process.
 

Objectives:
The audience will learn why Application Performance Management is a mandatory discipline in data centers and how the tuning process is working.

Outline:
Capacity Planning and Performance Management
The objectives of the Tuning Project
The Tuning Process
Measurements Deliverables
Results of the Tuning Project

Full Abstract:
The most important success criteria of a Performance Management Project is a well structured tuning process. Compuware has run many tuning projects in Central Europe and world wide. The cumulated experience is documented and applied in every project. Based on a real project Compuware demonstrates in this presentation the process, the deliverables and the key findings. As this project was performed in a complex environment (Cobol, CICS; DB2, Java, WAS, DDF...) the lecture guarantees to be interesting for a broad auditorium.

Objectives:
This presentation provides an overview of the major SQL-related enhancements introduced by DB2 9 for z/OS regarding data types and DML. These enhancements will help improve the productivity of SQL application programmers and allow better portability of applications.

Outline:
INTERSECT, EXCEPT
INSTEAD OF triggers
MERGE
SELECT FROM MERGE / UPDATE / DELETE
TRUNCATE
ORDER BY/FETCH FIRST in subselect
New data types: BIGINT, BINARY, VARBINARY, DECFLOAT

Objectives:
A new variation of SQL procedures, native SQL procedures, are introduced in DB2 9 for z/OS. Richer support of the SQL Procedural Language, and attention to the application development lifecycle, offer improved usability and portability. These extensions (including versioning and deployment capabilities) based on new technology can be a favorable alternative to the existing compilation of SQL Procedural Language procedures into an external C language implementation. Since native SQL procedures are managed by DB2 and run within the DB2 engine, there are also significant benefits in terms of improved performance, security, and reduced cost of ownership.

Outline:
Introduction
 Background and Motivation
 Comparing external vs native SQL procedures
New Features
 SQL Enhancements
 Versioning and Deployment
 Debugging
Performance Technologies