SQL in web service best practices?

Adding a max/min pool size allows SQL server to pool connections so even though you create a new SqlConnection object, the db can pool connections for you.

Adding a max/min pool size allows SQL server to pool connections so even though you create a new SqlConnection object, the db can pool connections for you. (MSDN, min pool size) eg. ConnectionString="Catalog=MyDb; MinPoolSize=10; MaxPoolSize=10...

Ok, I was just unaware of this feature. Thank you. – MainMa Dec 30 '09 at 3:40.

Personally, by default I would open the connection with each call, and rely on connection pooling to sort it out for me.

I wouldn't worry about the connection cost unless you are finding that to be problematic for some reason. Connection Pooling will make most of this less of a concern. If you are working heavily with the database, or retrieving a large amount of static data you might want to consider implementing some kind of caching to reduce the overall cost of contacting the database period.

The more data you can keep in the application cache the better, even with stateless web services.

Also be careful of how long the web service keep-alive setting is set to, so the cache is not refreshing too often and hindering performance. – Russell Dec 30 '09 at 3:38 Good point! Caching is one of those problems that introduces subtle other problems into a design.

– GrayWizardx Dec 30 '09 at 3:46.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.