jueves, 19 de julio de 2012 12:10
It seems (at least from what I have seen so far) that the Business Rules I can specify in DQS to evaluate Data Quality or cleanse data are quite simple and limited. We would need a more advanced way for specifying complex business rules and cleansing rules (cleansing could have complex algorithm characteristics). Other tools like Trillium, Ataccama are much more powerful in that regard. Is it possible to extend DQS with a customized Business Rules/DQ Provider (for cleansing, consistency checks, validity checks, standarization rules etc.)? What is the recommended approach here? Is a "Reference Data Service" intended for that purpose? If yes is there any documentation available how to implement a custom "reference data service"?
Thanks for your help in advance.
Todas las respuestas
jueves, 19 de julio de 2012 13:33Moderador
A custom Azure Datamarket RDS provider (can be shared amongst public paying customers), or standalone RDS provider (could be internal to your company and not public) is about the only extensibility to the cleansing process to add such rules in DQS. The API for rules is not open in this version (SQL Server 2012)
Azure RDS providers have to be onboarded with the help of the datamarket team, so its best to contact them for the detailed specs which they will provide since there are billing and other standards.
Non-Azure RDS can be done. I don't see the docs online thought. Its worth opening a connect item (connect.microsoft.com) or calling the support team to get the spec. I don't think its publically documented at present, probably just an oversight.
Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance
- Propuesto como respuesta Welly S LeeMicrosoft Employee, Moderator jueves, 02 de agosto de 2012 15:50
jueves, 02 de agosto de 2012 15:50Moderador
To clarify, Direct Online 3rd party reference data service is a planned future feature and is not yet a supported feature in SQL 2012.