All geek questions in one place

Is there a common OData provider for SQL Server?

I created a gadget for our CRM consultants that allows them to provide data from an oData source to CRM. At the moment, it will connect to any data source, but for client sites we need to develop an oData service using WCF each time for each data source.

Does anyone know if there is a worthy general tool that can retrieve data from SQL Server, present it (via IIS) as oData and which can be configured without Visual Studio by a non-developer?

+4
source share
1 answer

We (the WCF Data Services team) have heard about this several times; Following are a few of my thoughts in a specific order.

  • We have not heard much. There is reasonable work, and without sufficient requirements it is difficult to justify. However, there is nothing that would prevent the community from making efforts to achieve this (hint, hint :)).
  • There are a few questions you need to answer. For example, what are the default restrictions for a provider? Do you really want to allow arbitrary extensions on something that is probably on the production database server? What about permissions? How about reading / writing?
  • What happens to volatile circuits? Is this a fully dynamic provider? How much overhead does a database schema scan and how often should a database schema be checked?
  • How could customers use OData's dynamic service? Most customers use some form of code generation to facilitate interaction with the service.

These thoughts are not really intended to be discouraged at all, but I hope they give you some thoughts if you try to create a common provider yourself. If you do this, I will be happy to know about it.

+3
source

Source: https://habr.com/ru/post/1435308/

More articles:


All Articles