Microsoft MDS Stability

Data Architect at a non-profit with 1,001-5,000 employees
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. View full review »
Data Architect at a government with 10,001+ employees
The solution is very stable. View full review »
Decision Consultant at a consultancy with 1-10 employees
I have had some errors that seem to be related to memory usage when there is a lot of data. View full review »
Find out what your peers are saying about Microsoft MDS vs. Orchestra Networks EBX and other solutions. Updated: January 2020.
397,408 professionals have used our research since 2012.