Web服务，ADO.NET连接池，超时错误

If I have an .asmx Web Service that only exposes one call. One that takes a few params and inserts those values as a record in SQL Server 2005 table. What should that method look like to be as "kind" to the ADO.NET Connection Pool as possible? What should it look like if its going to be called maybe 10 times a second (spread out) over multiple clients. Any other settings I should tweak?If I have an .asmx Web Service that only expose