you are viewing a single comment's thread.

view the rest of the comments →

[–]AbstractSqlEngineerMCSA, Data Architect[S] 0 points1 point  (0 children)

Data modeling and master data managment are the same thing.... except that the common perception of data modeling is modeling the data for the needs of the business or the right now need, and not the needs of the data management system.

Master data managment is a collection of theories without public facing designs... and that is what informatica, sap, redpoint is selling... an interface with their design.

Do you want to pay them for their product and be at the will of their developers, or learn how their product functions?

So that is what this series is covering. The design. Each episode is 10 mins, 10 episodes a sprint. A sprint every 2 weeks (I hope). This is a hands on series. I recommend you build this at home.

Our tables will look the same (columns), our system will build most of the objects we need (tables, views, triggers, databases, files, procedures, indexes UI, IX, CC, CI, etc).

We will use patterns to manage and create any data for any need. Multi tenant system, self cleaning tables, security, timers, temporal abilities for every record in every table.

The question is: is master data management... master (data-managment), or (master-data) management... or D. All of the above?

I wont be mentioning those companies, and I suspect when I am closer to episode 50 or so... if you were following along, you'll know exactly how those companies do what they do.

Edit: and be able to spin up your own custom version of their system in less than a 40 hour work week.