SQL Server Web Service

cotton31 · 2 Jun 2011 at 15:37

Hi all,

Can anyone point me in the direction of a tutorial to learn about the above?

We have a database which I would like to write a mobile web app for, and have seen that a web service would be the best way to go to make the data accessible?

Correct me if I'm wrong!

Thanks,
Matt

Goksly · 2 Jun 2011 at 15:50

Unless something has changed, sql server doesn't have a web service. You would write a web service in another language, such as C#.net that the mobile apps would communicate with.
Access between the database and web service is as per any other web application.

cotton31 · 2 Jun 2011 at 16:08

Perhaps I've misunderstood then? I'm sure I've read it was something to do with security, and rather than connecting to the database, you'd 'push' the data you needed out via the web service.

I'm a complete novice at this - my only web app development has been in PHP/MySQL!

fez · 2 Jun 2011 at 18:56

Depends if you want to run an application on the same server as the sql server or if you wish to write an API to expose the data to outside sources. You don't have to be on the same server to query sql databases, you just need to allow exterior access to it. If you know what you are doing with it then there is little risk of allowing external connections to a sql server without an API filter.

AshenShugar1873 · 3 Jun 2011 at 17:20

I think you may be talking about endpoints in SQL Server. Endpoints create listening ports on the database server that expect SOAP requests and respond with data.

http://codebetter.com/raymondlewallen/2005/06/24/create-a-web-service-directly-from-sql-server-2005-using-an-http-endpoint/

I have endpoints set-up in work that respond to a php call and respond with data from an SQL stored procedure. The main problem is that php will need to provide the credentials in plain text to the database server so you need https.

If you are comfortable with php a better way would be to use the php MSSQL functions, or if you are wanting a new challenge throwing together a aspx page to speak to SQL server is another way to go.