Agree. Most often budget can dictate whether you query production systems
(keep it simple) or build another repository (whether that's a data
warehouse or copy of production that can then also be leveraged for a
disaster recovery requirement).
The main point is - we have tons of clients that just query production
systems/databases. But if you do, be aware of the performance implications
and learn how to do those things I suggested to avoid a natural conflict of
workloads (OLTP and complex queries).
Doug Mack
Analytics Consultant, DB2 for i
IBM Systems Lab Services
Mobile: 360-481-1271
email: mackd@xxxxxxxxxx
twitter: @mckdrmoly
From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 04/20/2016 05:14 AM
Subject: RE: BI / Reporting tools
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Jamal,
BI and DR are entirely too different things, and really need to be thought
of separately. There are several vendors on this list (Agile Included)
that
can help you however some quick thoughts:
What Doug was explaining is if a DBA is thinking about the data (regardless
of the Database OEM) then the DBA can set up the structures needed to keep
the production data safe and efficient. Security is baked into the plan.
With respect to Disaster Recovery (does that include High Availability?)
that implies a copy of the system and what you do is entirely dependent on
the recovery point, and recovery time objectives. Is the copy on another
system ready to take over within a very short amount of time, or is the
copy
on tape, where you would have to recover bare metal to get back to
production. Both are valid, but very different in the implementation.
A replicated system if licensed properly could also act as the second
repository for the BI initiative, but that requires a fair amount of up
front consideration and planning. It does not necessarily mean
significantly more expensive, just that it requires a good deal of thought.
The considerations you need to make really are no different in an Intel
environment vs. an enterprise system environment like POWER Systems; just
the implementation is different.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Aljahmi, Jamal
Sent: Wednesday, April 20, 2016 5:56 AM
To: midrange-l@xxxxxxxxxxxx
Subject: BI / Reporting tools
Thanks Jim and Doug.
If accessing date using production is not the recommended approach then
what
it best practice. Short of doing a data warehouse or restoring a backup to
a
different environment, what is best approach. My background is the window
environment, so forgive my lack of knowledge in the IBM series but I need
to
give direction to my group as we really don't have the right expertise.
Might be the right approach for me to bring an expert that can recommend
best approach. If anyone has used a 3rd party please let me know as I'm
focusing on BI and disaster recovery.
Jamal Aljahmi
Chief Information Officer
36th District Court
421 Madison Ave.
Detroit, MI 48226
(313) 965-2613
Jamal.aljahmi@xxxxxxxxxxxxxxxxxxxxx
www.36thdistrictcourt.org
------------------------------------------------------------------------
This message and any attachments originated from a computer at the 36th
District Court in the city of Detroit and are intended only for the use of
the addressee(s) and may contain information that is privileged and
confidential. If the reader of the message is not the intended recipient
or
an authorized representative of the intended recipient, you are hereby
notified that any dissemination of this communication is strictly
prohibited. If you received this communication in error, notify the sender
immediately by return email and delete the message and any attachments from
your system. Furthermore every effort has been taken to ensure protection
against virus infection; we cannot accept any responsibility for viruses.
Consequently, please ensure that all attachments are virus checked prior to
opening.
------------------------------------------------------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
midrange.com
