• Thanks for the quick reply! I understand your concerns. The scenario is a Silverlight application that will be shrink-wrap deployed in small offices with 1-3 users. The attached DB will be called into from the web service living on the web site the Silverlight app is downloaded from in the small office network. I was thinking about deployment more than performance, and was thinking that once the site is hit, the web service is attached to the dB and won't be re-attached until the ASP.Net worker process re-cycles. Am I incorrect in this last assumption?