Consider: IIS 7 Server 2008 SQL Server 2005 VS/VB.NET 2008
How can I connect to the database on the above box from a WCF web service being served (again, on the same machine), in such a way that the application does not try to logon/connect to the database each time it is invoked? In Java we call it "Connection Pooling", where a connection is made once, and the app served has fast access once that initial connection is made. This has to do with abstracting the datasources, defining them separately from the applications themselves. In .NET, I notice that examples always show the connection being made from _inside_ the app, or service in this case. Will IIS 7 inherently know how to do this, or is there some combination of application and server settings needed to make this happen? Should a heavily used service have the connection in the app, or is there a way to create the .NET equivalent of a WebSphere, WebLogic/JBoss 'datasource'? I really looked today for answers before coming here, and maybe I've missed all the places this exists. I'm hoping some of you here have had to have a web service hammered that access a database... TIA! pat :)
