I've been using SQL Server 2000 and am not familiar with all the new
features in 2005 but I understand it has the ability to make web
service calls.
Is there a way to write a stored procedure that passes street/city/
state data to a web service and returns latitude/longitude by simply
using a sproc?
Any help is appreciated.
lq
In SQL Server 2005 you can use HTTP endpoints to expose stored procedures or
user defined functions as Web methods. Here are a couple good articles that
describe that:
http://www.developer.com/db/article.php/3390241
http://www.devx.com/dbzone/Article/28525
However, seems you need to consume a Web service within a stored procedure,
not to expose. This can be accomplished in SQL Server 2005 via CLR (Common
Language Runtime). The articles below will show you examples of doing that:
http://www.simple-talk.com/sql/sql-server-2005/practical-sql -server-2005-clr-assemblies/
http://davidhayden.com/blog/dave/archive/2006/04/25/2924.asp x
http://blogs.msdn.com/sqlclr/archive/2005/07/25/Vineet.aspx
Although doable, SQL Server may not be the best place to make Web service
calls. Perhaps having an external application that makes the call and passes
results to SQL Server will be a better architecture.
HTH,
Plamen Ratchev
http://www.SQLStudio.com
Plamen,
Thanks for the response. These links are exactly what I was looking
for. I have an Access front end so I'm looking for a solution that
will not require a seperate dot.net application to call the web
service.
lq
On Dec 26, 3:20=A0pm, "Plamen Ratchev"
> In SQL Server 2005 you can use HTTP endpoints to expose stored procedures =
or
> user defined functions as Web methods. Here are a couple good articles tha=
t
> describe that:http://www.developer.com/db/article.php/3390241http://w ww.de=
vx.com/dbzone/Article/28525
>
> However, seems you need to consume a Web service within a stored procedure=
,
> not to expose. This can be accomplished in SQL Server 2005 via CLR (Common=
> Language Runtime). The articles below will show you examples of doing that=
:http://www.simple-talk.com/sql/sql-server-2005/practical-sq l-server-2...htt=
p://davidhayden.com/blog/dave/archive/2006/04/25/2924.aspxht tp://blogs.msdn.=
com/sqlclr/archive/2005/07/25/Vineet.aspx
>
> Although doable, SQL Server may not be the best place to make Web service
> calls. Perhaps having an external application that makes the call and pass=
es
> results to SQL Server will be a better architecture.
>
> HTH,
>
> Plamen Ratchevhttp://www.SQLStudio.com