When an enterprise first encounters master data management, it often doesn’t have a clear understanding of how MDM will affect the architecture of its business transaction systems or business intelligence systems. This article describes master data patterns in legacy system architectures, a general MDM architecture and some ways the new MDM layer affects the master data patterns in the legacy layers.
2009-06-19
2,401 reads
This white paper describes how application developers can leverage the functionality of Microsoft SQL Server 2005 Integration Services to address the data integration challenges of Master Data Management applications.
2008-01-18
1,821 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers