Moving web service into SQL Server 2005

May 30, 2007 at 9:56 PM
Hi,

What about moving all of the web service logic into the Sql Server.
If you are loading the assembly into the SQL Server into should work.
So you don't need to run another web app.

best regards
Christian
Coordinator
May 31, 2007 at 6:13 AM
I thought about that, but there might be a problem when it comes to hosting on a shared hosting provider. I don't have full access to all the sql2005 features (if there's even a 2005 server available); and with web services, I can pretty much host them anywhere I want as long as their accessible to the client.

It's not really all that bad running the central web app. You could rip out the functionality and splice it in with another web application if you wanted to. Then you could... say... host a corporate website with membership access, use the built-in aspnetsql membership provider, and then host your web services on top of that. Then it would serve as both membership for the website and for the web service clients, which is kind of what I intended it to be.

I may have to investigate that further though. I'm always open to ideas.

Thanks,
-Nathan


Volleyknaller wrote:
Hi,

What about moving all of the web service logic into the Sql Server.
If you are loading the assembly into the SQL Server into should work.
So you don't need to run another web app.

best regards
Christian

Jun 4, 2007 at 6:18 AM
Hi Nathan,

Forget my previous post.
In the SQl Server 2005 Express Edition you are not able to create HTTP endpoints. This feature isn't available in
the Express Edition. Your way is more general useable.

regards
Christian