In a few tutorials which I tried was a very specific dataset being used – the NYC 311 calls dataset. 311 calls in NYC are some sort of support calls to easen the caller rate on the emergency number 911. There are a lot of people calling this number over the time. The city of… Continue reading
A while ago I wrote about using MySQL as a database for Data Vault 2.0. Now, after some time passed and the dataset grew, it is time for a new evaluation.
Technologies and definitions inside of the Business Intelligence trade are changing. Data Warehouses are traditionally the way to generate data for evaluations and reports. But is this changing – and how?
I like patterns. One of the first patterns I learned about was MVC, or Model-View-Controller. For those who don’t know, very roughly: it separates storage logic from presentation logic. When you use it, you have inevitably separate storage and business logic. SQL does all at once. Oh, boy.
You thought it would be hard to go through a Business Intelligence project in an organization. Maybe it is easier than thought… when you change focus!
In the current past I see a lot of questions about Talend ETL and how to use it to map to dimensions and fact tables. Is that really feasible?
To implement Data Vault and its modelling technique, a database is required. Can MySQL cut it? What are important settings?
One question I read and talk a lot about is if it is neccessary at all to use a schema with data. So, is it important to model?
Ever wondered what Business Intelligence is? Is it important for your company? Find out here.
If you use Kimballs Star Schema and refer to it as your Data Warehouse, you should read on. I know, this is a bold claim to make. And everyone who has some experience in Data Warehousing might be surprised in what I mean. But sometimes, your Data Warehouse is not a Data Warehouse. Why?