We just raised a $30M Series A: Read our story

Microsoft MDS OverviewUNIXBusinessApplication

Microsoft MDS is the #2 ranked solution in our list of top Master Data Management (MDM) Software tools. It is most often compared to Informatica MDM: Microsoft MDS vs Informatica MDM

What is Microsoft MDS?

Master Data Services (MDS) is the SQL Server solution for master data management. Master data management (MDM) describes the efforts made by an organization to discover and define non-transactional lists of data, with the goal of compiling maintainable master lists. An MDM project generally includes an evaluation and restructuring of internal business processes along with the implementation of MDM technology. The result of a successful MDM solution is reliable, centralized data that can be analyzed, resulting in better business decisions.

Microsoft MDS is also known as Microsoft Master Data Services, Microsoft MDM, Microsoft SQL Server Master Data Services, MS MDS.

Microsoft MDS Buyer's Guide

Download the Microsoft MDS Buyer's Guide including reviews and more. Updated: October 2021

Microsoft MDS Customers

ETA a.s., Apeejay Surrendra Group, Blue Star Infotech, Rotherham Doncaster and South Humber NHS Foundation, The Sydney Children's Hospitals Network, New Belgium Brewing

Microsoft MDS Video

Pricing Advice

What users are saying about Microsoft MDS pricing:
  • "MDS is a part of the SQL Server enterprise license. I am not aware of any additional costs."
  • "With Microsoft, we buy everything though an agreement, so we purchase volume licensing every year."
  • "SAP is more expensive than Microsoft."
  • "The solution does require a license and we have enterprise licenses."
  • "I would like to see better pricing."

Microsoft MDS Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
GaryM
Data Architect at World Vision
Real User
Top 5Popular
MDS 2016 - Primitive but the price is right

What is our primary use case?

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.

How has it helped my organization?

It enables data stewards to directly interact with data on a web site or Excel without building a custom solution. This includes data stewards getting notification emails automatically when new data is loaded including a link to the specific data that needs to be updated. It also has a built-in single level of approval management that is used where versions of data need to be approved prior to publishing. The end result is more consistent data, more consistent data and fewer data silos.

Reference data management is integrated via using standard automated ETL processes extracting from the published database views. This eliminates the need for one-off, silo'd and uncontrolled data management. 

What is most valuable?

  • Ease of use
  • Excel interface
  • Simplicity
  • Soft delete support
  • Sophistication of business rules
  • Price (FREE for sql server enterprise license)
  • Hierarchy management 
  • Security integration with AD
  • Very fine grained security
  • Easy to build (and extendable) business rules
  • Automatic Notification
  • Versioning
  • Integrated boolean business rules
  • Change detection
  • Integrated workflow
  • Staging support
  • Publication support
  • Ability to propagate from one repository to another
  • Ability to share reference data across models
  • Integrates as a web part
  • Flexibility
  • Includes both batch staging process and Excel data loading
  • Unused area of hierarchies to easily identify members not assigned

What needs improvement?

  • Product Roadmap - it is unknown how Microsoft will support this tool long term as it now gets very few if any updates when new versions of SqlServer come out.  There is no known plan for Azure PaaS version.
  • It "can" have a bug where a model becomes corrupted.  It still operates but will no longer hard delete (purge function stops working) and can no longer migrate the model to another repository as the create or clone functions stop working.  It gives internal FK and duplicate row errors when attempting these functions.  
  • Another unpredictable bug:  Adding new attribute to entity doesn't show in web interface - only Excel.  Only known solution is to drop the entity and re-create it. Only experienced once so far.
  • Business Rules cannot prevent bad data entry!  Business rules cannot be used to prevent bad data from getting entered - it only marks the data as bad after it is saved because rules can only apply to data being saved.  And even then it requires the data steward to push a validate rules button.  If they forget they won't notice (and notifications won't go out) regarding rule violations.  In my 30+ years in IT I've never experienced a tool that only allows you to create reactive rules that identify bad data but never prevent it from getting saved. In a large enterprise I would rule this as a show stopper.
    • Bottom line:  Business rules need the ability to prevent data changes, not just validate saved changes
  • Second largest shortcoming:  Hierarchy integration views don't support custom attributes. This capability (which would be awesome if it worked right) is completely worthless without supporting custom attributes.
  • Explorer GUI is clunky and awkward.
  • Tool needs to get more frequent enhancements.  For example, since 2016 there has been no enhancement except replacing Silverlight in the 2019 version.
  • It needs the ability to publish only a single business rule. Publishing business rules requires publishing all rules and results in requirement for re-validation of all rules.  Until that is done the validation status on all affected records is in an "awaiting validation" state which can adversely affect data usage and validity.  
  • Needs ability to remove menu options that may not be relevant to data stewards such as Entity Dependencies, Collections or Changesets.
  • Needs ability to default user group's first screen.  For example defaulting to a specific hierarchy display.
  • Resolve a bug in the domain based validation business rule feature: the web interface will not allow correcting domain based lookups in the child properties (only works using hierarchy drag/drop or within Excel).
  • Hierarchy names should allow exceeding 30 characters.
  • Selecting child members within the navigator in a hierarchy results in the GUI just ignoring you... it should allow selecting children in the navigator or at least give an error message. (Note that 2012 version resulted in blank middle panel when this occurred rather than just ignoring you).
  • Needs to allow renaming the code and name attributes within the publication views (only allows renaming in the UI).
  • Derived hierarchy views should optionally include all attributes from all respective levels, not just the code and name attributes.
  • Needs to allow setting the CODE attribute datatype as numeric rather than forced datatype of string (which turns into nvarchar(250) behind the scenes). This is a significant headache as simple sorting on the CODE attribute with numbers causes numbers without leading zeros to not sort correctly and it requires adding business rule to enforce numeric datatype.
  • Needs to support setting view datatypes to varchar rather than forcing nvarchar so subsequent extracts do not have to do datatype conversion if not using unicode in your target database.
  • Versioning lacks granularity as it only supports model-level versioning.
  • The deployment migration GUI tool doesn't support data, only meta-data making the GUI export tool fairly useless. (Including data requires use of command line to support data)
  • The deployment migration tools do not support business rules requiring manual maintenance when using multiple environments (e.g. dev/sit/prod).
  • Excel plug-in needs to support hierarchies.
  • Needs to support email notification to more than one email group/user.
  • Staging process is non-intuitive and overly complicated.
  • Repository should utilize a prefix or unique schema for each model so that entities and views do not have to be uniquely named across models.
  • Needs ability to integrate seamlessly with data quality products. (DQS has some level of integration with MDS but the integration is overly complex and DQS's days are likely numbered).
  • Notification should work without an AD user first accessing the model. Once you setup the notification for an AD user or group it should just work without every user having to log on at least one time.  


For how long have I used the solution?

We have been using MDS in some capacity for around 10 years going back to 2008R2 version

What do I think about the stability of the solution?

No issues encountered with stability in terms of up time but one of our models won't send notifications just to specific users which appears to be a bug in the interface between MDS and SqlServer SMTP as MDS logs the notification but SqlServer does not log the email send (success or failure).

There is a bug if you set the CODE or NAME attribute security to read-only for a group that the admin is in, then administration capability disappears for that admin account. This can be reset in the backend repository but is a significant bug. Supposedly it was fixed in CU1 but was not.

Some business rules when attempting to use them cause vague database error that was also supposed to be fixed in SP1 but was not.

Notification stopped working after a couple of years. MDS is sending notification but it no longer communicates with SqlServer smtp even though SqlServer SMTP can be successfully run from other tools such as SqlAgent. It appears to have stopped working after a SqlServer patch.

What do I think about the scalability of the solution?

Our largest entity is a few million rows. It does not seem to scale well for any significant volumes.  I would hesitate to use the backend for CDI/customer purposes unless you have very small customer volumes.  Consider that if you're looking at Profisee Maestro solution since it shares the same backend database design.

How are customer service and technical support?

Customer Service:

Microsoft was incredible during beta testing but customer services hasn't been needed since much earlier versions that had installation bugs. Documentation online is missing some critical installation nuances such as SqlServer security settings needed in order to deploy models.

Technical Support:

There is a great amount of information available on the web for this product and its relatively simple so direct technical support has been rarely needed once we were off the beta version.

Which solution did I use previously and why did I switch?

We didn't have a previous solution. Any augmentation of source system data for reporting was done via spreadsheets. 

I find this product far superior to a previously used product which was Hyperion MDM, now Oracle MDM. Although Oracle has enhanced their product in recent years since I last used it it was built upon the dying Hyperion database and had no governance built in and no web interface.  And the Oracle tool is hundreds of thousands verses this tool which is free.  Need I say more?

Note that competing products in the market place are very expensive and will include possibly more sophistication than you need. This tool does everything you will need for simple dimension or reference data management purposes.

How was the initial setup?

It is fairly straightforward as the Excel plug-in makes the initial data load very simple.

What about the implementation team?

We implemented it in-house.

What was our ROI?

There was no cost for the software as it comes with SQL Server BI, and Enterprise editions. The ROI is terrific and it means you can avoid building or purchasing a solution.

What's my experience with pricing, setup cost, and licensing?

None as our in-house staff did the setup. There is no day to day maintenance needed. The 2016 version is no longer supported by modern browsers so high recommend only using the latest (2019) version available.

Which other solutions did I evaluate?

No as this was the only no-cost option with level of sophistication we needed.

What other advice do I have?

  • It's sweet spot is reference data. Attempting to use it for large scale customer data or products may be problematic.
  • The tool is integrated into Dynamics AX but there is not clear direction by Microsoft for improving and supporting the product as a stand alone long term. Use it with that knowledge and look for any indication from Microsoft that it will continue to support it or deprecate it.
  • If starting out I would not recommend using any version prior to 2019.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Suman Jupudi
Sr. Database Developer at Hill Physicians Medical Group
Real User
Top 5Leaderboard
Useful Excel plug-in, good scalability, and good integration with SQL Server and other Microsoft products

Pros and Cons

  • "It has a very good feature called Excel plug-in. You just have to install the plug-in, and then it directly connects to the MDS instance where you can maintain and manage your data and publish it right through Excel. You don't need to go to the front end to make any changes. It has easy integration with SQL Server, and you can use SSIS to do the ETLs. It is a part of the Microsoft stack. It works with most of the Microsoft stuff."
  • "The only drawback is that it does not have the matching, merging, and all true MDM components. For these, you have to use another competent called Data Quality Services (DQS). You need to plug it in and use it along with MDS for true MDM. Both of these are integrated together, but you have to do them separately, whereas, in Profisee, there are a couple of screens where you can configure the matching process, create matching rules, and other things, and everything is in one product, which is not the case with MDS. In order to implement a true MDM, you need MDS, DQS, and SSIS. You have to use MDS to store your golden records, DQS to configure and standardize all your rules and matching percentages, and SSIS to load the data to DQS and MDS. At the same time, you also need Melissa Data to clean up your addresses to validate and standardize the addresses. That's the main component of true MDM. It would be good if they can create a true matching component inside MDS and merge MDS and DQS."

What is our primary use case?

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.

What is most valuable?

It has a very good feature called Excel plug-in. You just have to install the plug-in, and then it directly connects to the MDS instance where you can maintain and manage your data and publish it right through Excel. You don't need to go to the front end to make any changes.

It has easy integration with SQL Server, and you can use SSIS to do the ETLs. It is a part of the Microsoft stack. It works with most of the Microsoft stuff.

What needs improvement?

The only drawback is that it does not have the matching, merging, and all true MDM components. For these, you have to use another competent called Data Quality Services (DQS). You need to plug it in and use it along with MDS for true MDM. Both of these are integrated together, but you have to do them separately, whereas, in Profisee, there are a couple of screens where you can configure the matching process, create matching rules, and other things, and everything is in one product, which is not the case with MDS. 

In order to implement a true MDM, you need MDS, DQS, and SSIS. You have to use MDS to store your golden records, DQS to configure and standardize all your rules and matching percentages, and SSIS to load the data to DQS and MDS. At the same time, you also need Melissa Data to clean up your addresses to validate and standardize the addresses. That's the main component of true MDM. It would be good if they can create a true matching component inside MDS and merge MDS and DQS.

For how long have I used the solution?

I've been using this solution for the last ten years.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It is pretty good. We initially built only 1 model and 10 entities, but currently, we are maintaining around 20 models and 300 entities.

We have around 50 to 75 people in our organization. They are mostly business analysts and people who are in the data governance team.

How was the initial setup?

Its initial setup is straightforward. It is just like on-prem. It took around one to one and a half hours because we had to spin up the Azure wheel. There are a couple of prerequisites that you need to do that takes around half an hour. After that, it is straightforward.

What about the implementation team?

I did it myself. I also handle its maintenance. I am the main point of contact for any troubleshooting, upgrades, or patches that we need to do.

What was our ROI?

It has been 200% useful in our organization.

What's my experience with pricing, setup cost, and licensing?

MDS is a part of the SQL Server enterprise license. I am not aware of any additional costs.

What other advice do I have?

I would highly recommend this solution. It is a very good tool. You don't need to implement a true MDM in order to implement MDS. You can automate a digital transformation where you can migrate your Excel and Access databases that are lying in silos to MDS. This way you would have true data governance, security, change tracking (CDC), and security versioning. There are a lot of features that are very beneficial. We'll be staying with MDS.

I would rate Microsoft MDS an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Learn what your peers think about Microsoft MDS. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
542,267 professionals have used our research since 2012.
Satyam Saxena
Senior Software Developer at a manufacturing company with 5,001-10,000 employees
Real User
Powerful with great customization; can sometimes be slow with synchronization issues

Pros and Cons

  • "Enables non-technical people to directly interact with the BI system."
  • "There are occasions when the solution maintains SD and we get duplications of MDS."

What is our primary use case?

I'm a distributor and developer of Microsoft MDS. 

What is most valuable?

The most valuable feature of the solution is Excel because it enables even non-technical people to directly interact with the BI system which is important because most of our people are not from the IT sector. The second important feature is that while we are using Informatica and other SAP tools which are less customizable, MDS increases customization for us and that is very useful. MDS, SQL and SSIS make the solution much more powerful. The main reason we use this solution is because of its customization. 

What needs improvement?

I have faced data primary violation in MDS when the primary key was full and that is not good. There are occasions when the solution maintains SD and we get duplications of MDS. When I use the SIS package for batch activity and it's full, I have to delete the batch manually by going into the database. The solution can sometimes be slow. We are in a healthcare environment and I've faced some synchronizing issues with the test model. I've faced some issues as a consultant of this solution because of the above. It can be slow sometimes.

I rate the solution six out of 10. 

For how long have I used the solution?

I've been using this solution for six years. 

What do I think about the stability of the solution?

There can be some issues with stability depending on how you use the solution. 

What do I think about the scalability of the solution?

We can directly scale everything by coding and we can customize everything. 

How was the initial setup?

It's important to remember that when you're installing the SQL Server, you have to select MDS. Once that's done MDS has to be enabled and the MDS database has to be created. For that purpose, you have to open MDS configuration and create the MDS database. Finally you have to build a few services of Microsoft Windows - Windows 10, Windows Server or something else - to enable multiple services and open multiple ports to enable DevOps MDS service. You then need a Microsoft Silverlight for MDS use. Finally, the MDS developer must have the admin rights of the system as well as the database.

What's my experience with pricing, setup cost, and licensing?

MDS alone is a free product, but it comes with the complete package of Microsoft SQL Server. So while you are purchasing SQL Server Pro version or licensed version of SQL Server you also get SSIS, MDS and DQS. 

What other advice do I have?

The advantage of Microsoft MDS is that it's so handy, so customizable, and easy to use. It has all the basics and given that we are a directly integral system, everyone is able to use Excel. The advantage is that you can be working on bulk data and creating a batch, we can upload or deliver activities. If one system has reached capacity or has stopped, then the whole system stops and it is quite difficult to solve the problem. My advice is that if you want to use custom UI, then make sure you work on Internet Explorer. Without it you can't use a structured MDS UI. In place of Internet Explorer create your own custom UI by the .NET feature.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
NipunaMaliga
Systems Specialist at Zillione Technology
Real User
Top 10
Has good replication, availability, and clustering features

Pros and Cons

  • "Its availability for a secured server is one of its most valuable features. Also its replications - we can manage eight replicas. Their clustering and availability groups are also valuable."
  • "They do not offer the SQL Server Management tool via the installation. It is a separate tool I use when I'm trying to configure the mirroring with SQL Server Mirroring. This is not supported and I'm getting some errors on the database mirroring."

What is our primary use case?

Mainly, I do infrastructure support. We do fine-tuning, information, configuration, higher-level availability, and replication. Also, single and clustering solutions - both kinds.

We do on-premises and cloud deployments. This is because some customers use Microsoft Azure, mainly in the financial sector, such as the Sri Lanka Government, who has many databases that cannot go on the cloud. The financial sector also works with on-prem databases.

I am mainly using the SQL Server from 2019. That's the latest version since last January while our customers are mainly using the 2016 and 2017 versions. This is because we are not providing the latest version. We are testing some bugs now. In terms of functionality, I think the 2017 version is better. I have not fully tested the 2019, so I cannot give a recommendation for it.

What is most valuable?

Its availability for a secured server is one of its most valuable features. Also its replication features are valuable- we can manage eight replicas. Their clustering and availability groups are also valuable.

What needs improvement?

They do not offer the SQL Server Management tool via the installation. It is a separate tool I use when I'm trying to configure the mirroring with SQL Server Mirroring. This is not supported and I'm getting some errors on the database mirroring. So sometimes I use the 2014 management console and the 2017 server for that. If the customer does not agree to that, I use a query for the database mirroring connections.

Additionally, I think some kind of machine learning related feature should be included. This is because technology is moving fast and all of the customers are getting it easier. So developers are making machine learning products. That's why they should include some kind of a machine learning feature here, too.

How was the initial setup?

Which initial setup are you referring too? It has multiple solutions and installations, some of which are very simple. Clustering is very difficult to setup.

Setup time depends on the customer's environment, including database size, the number of databases, and the amount of data. Last week I did a PLC with two databases and one availability crew. It took two days because one day I did clustering. It can be done in one day but the customer provides another day for that.

Also, because the customers haven't kept some downtime, we request some kind of downtime for the primary server. So sometimes we plan downtime when we need some days for the complete environment.

What about the implementation team?

I'm working with Microsoft solutions in Sri Lanka. We have a technical team for the DB side only - Microsoft SQL Servers, Azure platform, SQL servers. All of those have a security device. And as I mentioned, installation is per requirement. There is no need for a couple of engineers for that.

In terms of maintenance after the deployment, it also varies depending on the number of databases.

What other advice do I have?

On a scale of one to ten, I would rate Microsoft MDS an eight. I'd give it an 8 and not a 10 because it lacks some features, such as machine learning.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
KS
System Engineer at a university with 1,001-5,000 employees
Real User
Top 10
Easy to deploy and provision a machine, good analytics, but the pricing could be improved

Pros and Cons

  • "It is very easy to deploy and provision a machine."
  • "Most of the Microsoft partners, especially digitally, are separate. Personnel are business people, and they do not have technical expertise, so you end up as a company spending a lot of money training your staff and your engineers."

What is most valuable?

I like the ease of deployment. It is very easy to deploy and provision a machine.

I like the analytics and that I can run them. Until now, this was always something that was done on the business side. For me, this solution makes it easier to do analytics.

With Oracle, they have to use an IBM business intelligence tool called Cognizer. But with Microsoft, the BI tool is better. So we are using Microsoft BI as it is quite good.

What needs improvement?

Most of the Microsoft partners, especially digitally, are separate. Personnel are business people, and they do not have technical expertise, so you end up as a company spending a lot of money training your staff and your engineers. This is something that Mircosoft needs to improve on. They must have personnel who have each shared capacity for their staff, so when it comes to implementation, it doesn't take a lot of time.

The implementation takes months, and it could even take as long as a year. The implementation is a small issue because Microsoft does not come to the ground, it is the personnel.

The only issue is pricing because technical support is there. Our engineers are well trained in Microsoft, and we have the Microsoft BI Office which is very helpful but pricing is a bit of a challenge.

There is not much to be corrected other than just improve continuously on the business intelligence section. That is important for businesses.

For how long have I used the solution?

This solution was already in place when I arrived, and I have been working with it for more than ten years.

How are customer service and technical support?

Technical support is okay, we have not had any problems. In the future, we plan to move to Office 365. In the next financial year, we will be purchasing the license for Office 365.

What's my experience with pricing, setup cost, and licensing?

With Microsoft, we buy everything though an agreement, so we purchase volume licensing every year. That is how our licenses are managed.

What other advice do I have?

I am an information security analyst and I research to stay up on the trends and to see what is happing on the market now because we run our Firewalls.

I would recommend getting the correct licenses. From the article, they should get to know which licenses, because there are different agents of licensing. 

Ensure they get the right size servers.

Ensure that they have the best technical expertise, to help with the implementation.

Microsoft products are quite good. We run innovation Microsoft 2017 and it's pretty impressive.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Ariful Mondal
Consulting Practice Partner - Data, Analytics & Artificial Intelligence at Wipro Ltd
Real User
Top 5Leaderboard
Flexible, stable, scalable, includes an Excel API add-in, and the support is good

Pros and Cons

  • "It's very easy to use."
  • "It would be a better option to have an on-cloud version."

What is our primary use case?

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.

What is most valuable?

It gives you the flexibility to have in-depth experience. It allows you to collect data and save it as a golden record. You have the flexibility for data stewardship.

They also have an Excel API where you can do everything from Excel. You can make changes with the connectivity on the Excel API.

It's very easy to use.

What needs improvement?

The version that I work with is on-premises and it required an additional virtual machine on the cloud. It would be a better option to have an on-cloud version.

For how long have I used the solution?

I have been using this solution for three years.

We are using the latest version.

What do I think about the stability of the solution?

It's very stable. Stability is one of the best features.

What do I think about the scalability of the solution?

It's scalable. It's based on Microsoft SQL Server.

They are using this solution at an enterprise level for our customer who is an implementer. They are going to produce data and scale it.

How are customer service and technical support?

We contacted technical support with an issue that we were having and they were able to solve it. It was a learning phase but Microsoft provided support.

Microsoft support is good. They are customer-friendly and they are knowledgeable.

Which solution did I use previously and why did I switch?

We are using SAP for the master data.

SAP is more expensive than Microsoft. It's costly.

SAP is a very good ESP tool that can also be used for master data services.

It's very stable.

How was the initial setup?

I was not a part of the installation. I have not done it, but it should be simple. 

It's similar to any SQL server installation.

Implementing with the cloud was a little bit complex. 

There was an issue with the production version.

What other advice do I have?

In my current organization, I'm recommending reviewing all of the product cataloging master data management. This is what I would recommend for anybody who wants to do master data management, they use this product.

I would rate Microsoft MDS an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
MT
Individual Contributor at a pharma/biotech company with 1,001-5,000 employees
Real User
Top 20
Integrates well, scalable, and reliable

Pros and Cons

  • "One of the main features I have found useful is the integration with Azure active directory."
  • "I do not like using Silverlight and Internet Explorer. The new 2019 version gets rid of that, which is one of the reasons why we are looking to switch."

What is most valuable?

One of the main features I have found useful is the integration with Azure active directory.

What needs improvement?

I would like to separate the website from the database side. By default, you have the webserver running on the same server as it is the database. This forces us to make a bigger VM which means more costing for the VM. We tried to go with a less expensive route and every now and then we run out of memory, you have to reboot the machine. It is okay in DEV and QA, but ideally, we should not have this happening.

I do not like using Silverlight and Internet Explorer. The new 2019 version gets rid of that, which is one of the reasons why we are looking to switch.

Additionally, the overall performance could improve.

For how long have I used the solution?

I have been using the solution for two years.

What do I think about the stability of the solution?

The solution will work fine stability wise if you have the VM sized appropriately.

What do I think about the scalability of the solution?

If you have the environment then the solution can be scaled.

How are customer service and technical support?

I have not needed to call technical support but I almost did when I was trying to do a SQL server restore of a production database and converting it into a DEV and QA environment.

How was the initial setup?

I set it up on my own laptop and I did not think it was that difficult. The challenging part is making sure you are matched up with the right version and patch level of SQL Server and IE.

What about the implementation team?

I did the implementation myself and it took me two days because we had multiple versions of the documentation. They were all dated in their own unique ways and because of this, I created a new version of them all, that worked for me. We have three technicians that support the solution in my organization.

What was our ROI?

I believe my organization has had a return on investment using this solution.

What's my experience with pricing, setup cost, and licensing?

The solution does require a license and we have enterprise licenses.

What other advice do I have?

I rate Microsoft MDS a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PaulOhuche
Owner at PARA SYSTEMS LTD
Reseller
Top 5
Has a huge database with many users

Pros and Cons

  • "What I like about Microsoft, is that it has a huge database with many users."

    What is our primary use case?

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

    What is most valuable?

    What I like about Microsoft, is that it has a huge database with many users.

    What needs improvement?

    I would like to see better pricing - a drop in price would be great. 

    For how long have I used the solution?

    I have been working on Microsoft MDS for the past three years now.

    How are customer service and technical support?

    The technical support is good. We are responsible for the maintenance of the program for our clients, and I believe that we've provided good support so far.

    What's my experience with pricing, setup cost, and licensing?

    The price of the program has gone up, so I would like to see better pricing. But I like it that there are no additional fees that we have to pay.

    What other advice do I have?

    If I have to rate this program from one to ten, I will give it an eight. My advice to others would be to use an activity log. They should have a user account and they should keep track of every user that logs on, and the platform should keep track of it.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Microsoft Azure
    Disclosure: My company has a business relationship with this vendor other than being a customer: reseller