Understanding of data cache Dependencies

Recently, I have studied the data cache dependencies provided in Asp.net 2.0 and want to discuss some issues with you.
(1) A lot of materials are always saying "SQL cache invalidation", but in my opinion, all SQL cache invalidation is database dependent cache, and its core implementation is sqlcachedependency. Don't you know this idea, right? Is it SQL cache invalidation that not only contains database cache dependencies, but also includes something else?
(2) database dependent cache is designed for SQL Server 7/2000/MSDE/2005. The implementation step is to first configure the command line, that is, use aspnet_regsql, and then configure the section of the web. config file. The last step is the specific application. These configurations are implemented only when SQL Server 7/2000/MSDE/is used. For SQL Server 2005, these specific configurations (the first two steps) are not required, what about applications that directly rely on database cache?
(3) is the database cache dependency valid only for common SQL statements, and is it ineffective for data changes caused by stored procedures? In SQL Server 7/2000/MSDE, it can only be effective for common SQL statements, but can be applied to stored procedures in SQL Server 2005?
(4) In the implementation of database cache dependencies for SQL Server 7/2000/MSDE, some triggers and data tables are used for regular queries to detect whether data has changed. In SQL Server 2005, how does one implement it?