My concern, like the other posters, would be how you handle database changes.Performance gains are clearly evident via caching, but with a system with many users - certainly in our environment - the lookups we would most likely wish to cache are from the largest and most volatile of our tables.I am fairly new to .net, and would be interested to hear if anyone has an elegant solution that would all