Hi everyone!

I am planning a Caching Implementation for an Object-Persistance Framework.
Because the Framework is .Net 2.0 and SQL 2005 only, it would be possible to
use the SqlDependency Class to invalidate Rows within the cache that have
been changed.

Can anybody tell me at want cost this very comfortable feature comes? May it
be a problem to keep about 10.000 instances of SqlDependency Object within
the Client / Server?


GP

temporarily allow duplicate keys?
Multiple tab-delimited files without knowing structure
Dataview Sort
CurrencyManager marks all rows as Modified during navigation
OracleConnection error