Generally one does not just use a webservice for data access. Generally one will treat the webservice as a facade and hide things such as business logic and caching behind it. There are many benefits to doing this such as deployment, reusability, security, and believe it or performance can also be a benefit.
Note though that I am talking about using a facade not a webservice that simply brokers data from a sql server (which imho is a bad idea). When you get into performance, your application design (especially dealing with how well your calls match up to your needs) is what will be the key. There will be an obvious performance loss on large sets due to the XML size overhead in comparison with a binary transfer but one could also use something like WCF to support both XML and binary transfers (internal vs external consumers etc). On 4/17/07, Shane Courtrille <[EMAIL PROTECTED]> wrote:
Has anyone seen numbers on using a web service as an intermediary for your data access vs directly accessing SQL server? In an internet environment I think web services are a must in terms of security and just the basic act of connecting. Not many places are willing (or should) open the ports that SQL server needs. But in an internal network I have definite questions over which is preferable. Thanks, Shane =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
-- Studying for the Turing test =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
