It is stable.

The solution is very stable.

The solution is stable.

Microsoft MDS is generally a stable solution, but it can be fragile at times. If you are not attentive or make a mistake, it can cause problems. I have made mistakes in the past, but if I am very careful, it is not a big deal, and it does the job.

The solution is stable and I rate the stability an eight out of ten.

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.

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

It's stable enough. That's not a problem. It's reliable. There are no bugs or glitches. 

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

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

Microsoft MDS is stable.

I rate the stability of Microsoft MDS a nine out of ten.

The solution is very stable.

I have had some errors that seem to be related to memory usage when there is a lot of data.

No issues encountered.

The product is very stable.