Please share with the community what you think needs improvement with Microsoft MDS.
What are its weaknesses? What would you like to see changed in a future version?
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.
I would like to see better pricing - a drop in price would be great.
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.
In the next version, I would like to see integration with Azure. The duplication feature is not so good. The merge function should be improved to include better automation. For example, if two people have the same name, address, or mobile number then the records should be automatically merged. As it is now, I have to merge these records manually. I would like to be able to generate a report of current operations.
The solution could be better integrated into Microsoft's other products. One of the key features that it doesn't have is a data modeling feature. Everyone uses Microsoft, but not for modeling. They use IBM, SAP PowerDesigner, etc. It would be really good to combine this solution with a modeler. For me, that's what is missing. In a future release, I would like to see a better link to SSIS, Microsoft's business intelligence product. I would also like to see improvements in the user interface.
* Largest shortcoming: Business rules cannot be used to prevent bad data from getting entered. Rules can only apply to data already 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). * Need to be able to do nNotification 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 logging on at least one time first.