We use it to maintain our master data sets. We do a lot of setup files and crosswalk files.

We are using SQL Server 2016. It is on-prem till the recent version because SQL Server 2016 is on-prem, but from SQL Server 2019 onwards, it is compatible with Azure. I did a POC last month on the new version to host it up in Azure. We had both public and private clouds.

We used MDS to maintain master data created for the sales team using lists from D&B. MDS is also used to create an inventory of all the processes and data elements created to help the mastering process.

We integrated data from different sources for analytics. Some of the data elements have the same business value. However, the attributed names are different. After some cleansing in DQS, the data is persisted in MDS, where it is further evaluated against some business rules, which we cannot do in DQS. The data steward is also involved in analyzing the MDS errors, correcting, approving, and rejecting records. The output of this exercise is to create a single version of the truth for our dimensions for the EDW.

We've used MDS to maintain reference data used by ETL processes during data integration and transformation.

I use this solution to simplify master data management which makes it easy to create and maintain consistent master data without manual work. It supports data modeling, change tracking, and validation rules, all on the SQL Server platform. Unlike specialized tools, MDS is adaptable for various industries, making it a versatile choice for master data management.

It supports our production lifecycle, machinery management, registration, and distribution processes.

We primarily use this solution to process external repos and MDS. The data model is useful to us and is created within our company by our data modelling team. The Microsoft MDS tool uploads the data into the schema from the JMD repository and then generates the MI reports.

We use MDS for analytical and operational enterprise reference data management including management of campaign, product and financial management hierarchies.  We currently only use batch interfaces to feed or get data from it. We also use it to maintain source to enterprise data mappings that are fed to ETL via a generic RDM (Reference Data Management) design. We have a variety of data stewards who use the tool for data management and they get automatically notified via email with a link when new products need hierarchy assignment.

Microsoft MDS helps to record and save data to tables. 

It can be used for all the data cataloging, master data management, manufacturing, product management, data harmonization, data stewardship, for any kind of master data, and product catalog.

We use it in our company. 

We use the product for data migration, production, and development. We deliver data sources to our customers using MDS. We are a data company.

I'm a distributor and developer of Microsoft MDS. 

I'm using Microsoft MDS for configuring the storage for backups on the DPM server, and data protection manager.

Our primary use case of this solution is to develop solutions for our clients.

Our primary use case is to have a database of customers. We also use it to manage accounts.

We have an on-premises deployment.