background preloader

DWH/BI/PM Methodik & Konzeption

Facebook Twitter

Power BI and SAP – What Works and What Doesn’t – business intelligist. I run many workshops focused on integration of Microsoft Analytics and SAP.

Power BI and SAP – What Works and What Doesn’t – business intelligist

This is not an easy topic to cover due to complexities of the SAP landscape and also because Microsoft Analytics has many moving parts both with respect to its on premise and cloud components. In this article, I will just focus on Power BI and SAP ECC, Hana and BW. * – the word on the street is that these NOs are expected to become YES soon The following is a list of random points that are good to know as you implement a Power BI solution against SAP, in no particular order: The SAPPHIRE 2017 is just around the corner; I am looking forward to additional roadmap information becoming available around that time. Hahne kurze BIS 01 12. Why the NoSQL Movement Should Have Been Called the JSON Movement. By Andy Palmer, Co-founder and CEO of Tamr We all know by now that most “big data” challenges can be characterized into one of the “3 V’s”: Volume: You have too much data Velocity: It is coming at you too fast Variety: It is coming at you from too many places/silos Over the past 5 years, my partner Mike Stonebraker and I have been on a mission to raise awareness of the problems associated with Variety in enterprise data.

Why the NoSQL Movement Should Have Been Called the JSON Movement

We started by doing some research at MIT/CSAIL, working closely with Trifacta co-founder Joe Hellerstein. Now that we’re three years into Tamr’s commercial efforts, it’s worth sharing a few thoughts about the state of enterprise data and the potential for large enterprises to compete on integrated analytics. Let me describe why investment in these areas supports the long-term value of enterprise data and will help companies compete on integrated analytics in a sustainable way: I. The result? To realize the analytical potential of the enterprise, systems instead need: SQL vs NoSQL: The Differences. SQL (Structured Query Language) databases have been a primary data storage mechanism for more than four decades.

SQL vs NoSQL: The Differences

Usage exploded in the late 1990s with the rise of web applications and open-source options such as MySQL, PostgreSQL and SQLite. NoSQL databases have existed since the 1960s, but have been recently gaining traction with popular options such as MongoDB, CouchDB, Redis and Apache Cassandra. You’ll find many tutorials explaining how to use a particular flavor of SQL or NoSQL, but few discuss why you should choose one in preference to the other. I hope to fill that gap. In this article, we’ll cover the fundamental differences.

Most examples apply to the popular MySQL SQL and MongoDB NoSQL database systems. The SQL vs NoSQL Holy War Before we go further, let’s dispel a number of myths … How "Good" is Your Data Model?: Validating a Database Design to Pass the Test of Time - Safari Blog. By Steve Hoberman Steve Hoberman is the author of the recently released “Data Model Scorecard: Applying the Industry Standard on Data Model Quality” which is published by Technics Publications.

How "Good" is Your Data Model?: Validating a Database Design to Pass the Test of Time - Safari Blog

He also teaches the “Data Modeling Master Class” which is a leading data modeling course in the industry. He is the founder of the Design Challenges group, Conference Chair of the Data Modeling Zone conference, and recipient of the 2012 Data Administration Management Association (DAMA) International Professional Achievement Award. For many years I have been reviewing data models. A data model is a diagram (along with supporting documentation) that describes business terms (such as Order and Product) and the relationships between these terms (such as a Product may appear on many Orders).

I created the Data Model Scorecard to proactively determine how “good” a data model, and therefore improve the structures before the database and code work have begun. BI-Architektur – Konzepte und praktische Umsetzung – Winfwiki. Aus Winfwiki 1 Einleitung 1.1 Zielsetzung und Abgrenzung Ziel der Fallstudie ist es in einem ersten Schwerpunkt, die Konzepte, die sich hinter dem Begriff "Business Intelligence" verbergen, zu beleuchten und ein Grundverständnis zunächst einmal des Begriffes selbst und anschließend der Architektur moderner BI-Systeme im Allgemeinen zu schaffen.

BI-Architektur – Konzepte und praktische Umsetzung – Winfwiki

Dabei liegt der Fokus auf den allgemeingültigen theoretischen Architekturkonzepten der Business Intelligence und es werden keine konkreten herstellerspezifischen Konzepte betrachtet. In einem zweiten Schwerpunkt werden Konzepte der praktischen Umsetzung vorgestellt, d.h. unter welchen Voraussetzungen sind gewisse Architekturkonzepte gut geeignet oder weniger gut geeignet. 1.2 Vorgehensweise.

DWH Automation

Did you Buy a Self-Service BI Fantasy? As I gaze outside my quiet home office window watching an alligator in the pond, I am reminded of my mostly isolated virtual reality.

Did you Buy a Self-Service BI Fantasy?

Not even a rare splurge on chocolate chip cookie dough cheered me up. Thank goodness for IT/Dev Connections next week! Even introverts need to socialize a little bit to stay sane. Speaking of sanity, I continue to hear insane expectations that self-service BI tools can replace the need for a data warehouse. Three groups from different areas of the world discussed that topic with me recently. “I like nonsense, it wakes up brain cells.


Project Management. Microservices. "Microservices" - yet another new term on the crowded streets of software architecture.


Although our natural inclination is to pass such things by with a contemptuous glance, this bit of terminology describes a style of software systems that we are finding more and more appealing. We've seen many projects use this style in the last few years, and results so far have been positive, so much so that for many of our colleagues this is becoming the default style for building enterprise applications. Sadly, however, there's not much information that outlines what the microservice style is and how to do it. In short, the microservice architectural style [1] is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API.

These services are built around business capabilities and independently deployable by fully automated deployment machinery.

Data Vault

Data Governance. BI Strategy. Agile. Requirements Engineering. Kimball. Business Information Design.