Please enable JavaScript.
Coggle requires JavaScript to display documents.
Production issues Incidents (Complexity (Many unused objects are loaded…
Production issues
Incidents
Complexity
Many unused objects
are loaded into ODS
SSIS packages using lookup and merge
load and delete tables to Insert and update
procedure to set enddate
instead of
single TSQL merge statement
More difficult (possible errors) to deploy if only part of table changes needs to be released (manualy changing package)
Entity (IS) layer
with relationship tables
(add ID in table?)
Full load
Entity (IS) and DM are truncated and rebuild
How can you see what have been reported before?
Full load and incremental load
result in different enddate of records
(e.g. entity.Currency_FX)
ODS via generated merge statements
but entity (IS) done via SSIS lookup
Repeating logic
Datamarts for different Business Areas
where in all DM contract dimension and customer dimension
are loaded.
Ticket / issue handling
Communication
Tickets / incident handling
Can you pick up this 'odd job'
Not taken seriously as something to solve
and add value to the information system
Reduce number of incidents
Quantity seems more important than quality
Add logic on reports just in the queries instead of in the DWH
'Quick fixes'
Filter out records which causing errors
Documentation on tickets
Assigned to / action
Planning
Status :star:2
Project / incident lead time is often long due to
missing planning
communication via email
waiting for action / unclear who needs to take action
:star:3
Business Knowledge
Questions
Understanding the business
Challenge the request
If asked to show different view of a report for a specific client
it is suggested to make a new report just for this client.
No questions are asked why this client should be shown differently :star:1
Not only develop code as requested,
but also understand (functionally) what the
business is asking for and see if you
can create business value.
No consistent use of terminology
Unclear definitions
Aggregation not on correct level
e.g. PD/LGD on facility level.
e.g. adding an interest schedule to a report
aggregated on loan level (result in redundant info)
Development
Deployement
Release planning on white board
Logging work
Changes for incidents are
tracked by developers.
Everyone using own method.
e.g. list of objects in mail or file
OTAP
environment does not exist
Development to Production
A test/acceptance environment has been created,
but is in use for different project.
Status availability unknown.
Versioning
SSIS packages converted to 2012 version on production
TFS still contains the 2008 version.
Production failures due to deploying old versions to new production server.
Manually created or copied procedures
which can easily be generated
Error handling
SSIS error logging on all running child packages
if one of the child packages fails.
Errors often due to dataconversion
No tooling or metadata queries to check
possible dataconversion issues
Duplication errors often logged on higher layer
due to missing BK in lower layer.
Error on incremental load
sometimes solved by just restarting
or doing a full load.
Architecture / documentation
Check where data in object is coming from
is done by looking into code. No documentation
or tooling to provide these views.
Performance
Unused objects are loaded into DWH
SSIS packages using lookup and merge
TSQL merge statement used to perform better
Many reports directly build of ODS layer