calling SQL Server Endpoint web service - json

I understand that SQL Server endpoint returns data using SOAP.
Does anyone know if they can return JSON data?
Thanks!

Native HTTP endpoints can only return SOAP messages.
However it's possible to switch off the generation of the SOAP envelope, if you specify FORMAT = NONE in the FOR SOAP section of the declaration.
You could use this to provide an HTTP wrapper to your own stored procedure(s) which JSON-ise SQL server data (see books online for a detailed description of the very specific requirements your procedure must fulfill).
You should be aware that native endpoints are deprecated in SQL 2008.

No, unfortunately they don't support JSON.

Related

define a link (GET) on trigger

How can I send my mysql table parameters to a link through GET?
e.x. : http:/example.com/Send.ashx?id=[member.id]&name=[class.name]
You cannot access MySQL via http directly. You will need to set up a rest API server that handles http requests, makes the corresponding SQL queries, formats the result (typically as json or XML) and sends it back to the client.
In case you already have an API / web server, we need more detailed information on your setup

Call rest service that returns JSON in mule esb?

How to call a rest service that returns JSON in a APIKit based message flow. I want to prepare the request for Rest service and want to extract the JSON message in a message flow.
Can any one help me to do this?
Thanks
The recommended way to invoke/consume REST services in mule is the use of HTTP Request
Do let us know if there is a specific you are facing
The request connector is especially handy when consuming a RESTful API
that is described in a RAML file. If you reference the API's RAML file
in the connector's configuration, it will proactively offer you the
set of available resources and operations contained in the RAML file,
as well as enforce the policies described in the file. It will also
expose the API metadata to Studio, which can then be used by other
elements such as DataWeave to autocomplete fields and make
configuration much easier
Use Rest URI path to invoke the Service and you can also get json response as output based on the type of service you invoke

How to use Delphi to sign REST requests using HMAC-SHA256

I'm attempting to query an REST service with fairly limited idea of how to approach it.
I'm using Delphi XE6 (upd 1)
The company providing the API have said that: "The API is implemented as JSON via SSL"
and they go on to say that:
Access to any API endpoint requires authentication via signed requests, created with publicand secret API
keys
I have the keys defined above.
The signature is an HMAC­SHA256 hash of a string containing the request content­type, host,
URL, date timestamp (matching the request Date header) and request content (eg POST
parameters) separated by a single newline, and passed with the public key in a custom header
X­API­Authorization along with the public key, in the format PUBLICKEY:SIGNATURE
I understand each request needs to be signed.
How do I sign an http request with Delphi XE6?
The confusion for me at the moment is it seems Delphi has a number of built-in components have accessing RSET servers and parsing the JSON returned. I can't see any obvious way of signing requests using these components.
Specifically is there any help from the built-in Rest components or do I have to provide my own solution?

WCF Service not returning results while stored procedure does. How can I debug?

I have implemented a WCF service (written in C#) that serves as a backend to a Webapp. The WCF is supposed to call stored procedures from a SQL database and return the data via JSON so it can be displayed in the WebApp. My issue is that the WCF service sometimes will return an empty JSON array. If I use the same parameters and execute the stored procedure using SQL Management Studio I get hundreds of rows returned. How can I debug this issue? I've been looking at Chrome's dev tools and Firebug and they both show that the request is being responded too (it's just empty).
Thanks for the help.
There's three main places you can debug:
Use the WCF test client to call the service directly rather than from front-end code.
Use SQL Server profiler to make sure your service is calling the sprocs with the parameters you expect.
Attach the debugger to your WCF service and step through the code.
Attach a debugger to the WCF service and see what happens to the result set provided by the DB.

WCF Data Services ODATA throwing error with JSONP

Ok so I have a WCF ODATA service hosted locally for testing purposes. Then I have a Kendo Grid trying to query the service using a Kendo Datasource configured for ODATA exactly like the demo!
On the deployed service, I also implemented the "JSONPSupportBehavior" attribute and class that everyone is talking about!
Still I get this in Fiddler : A supported MIME type could not be found that matches the acceptable MIME types for the request. The supported type(s) 'application/atom+xml;type=feed, application/atom+xml, application/json;odata=verbose' do not match any of the acceptable MIME types 'application/json'
Is this IIS issue now or something else? This is driving me crazy!
This is a change made in the WCF Data Services release. In order to get JSON response back (or JSONP) you need to send Accept header with value application/json;odata=verbose. Pure "application/json" is now reserved for the soon to be coming JSON Light format.
See http://blogs.msdn.com/b/astoriateam/archive/2012/04/11/what-happened-to-application-json-in-wcf-ds-5-0.aspx for more details.