Rob Howard talks about the new database cache features in ASP.NET 2.0.

Currently one of the downsides of caching data is that your cache doesn't know if the data has changed. So you might end up with a ten minute latency to getÂfresh data updates appearing on a web site. The new version of ASP.NET is more data aware :

<%@ outputcache duration="3600" varybyparam="none" sqldependency="MyDatabase:Authors" %>

From the looks of this your ASP.NET application would need SELECT access on the table, which may not be ideal.

In the past I have seen some cool workarounds for this though, one used an extended stored proc to "touch" a text file. The extended proc could be called by a trigger when a table was updated. ASP.NET can watch the specified file and invalidate the cache when the file changes.