I am searching for material on database design methodologies concerning databases usage in an N-Tier architecture. We are currently studying the feasability of transporting out Client-Server Suite of applications to .net architecture with layers for Presentation - Business Logic - Data Store.
Most of what I find are discussions on Upward and Outward Scalability which deal with hardware configurations and partitioning data across servers. I am also interested in database design as well. I am looking for information on such topics as Stored Procedure/Trigger Usage in Very large Databases. What business rules are optimally handled in the database layer. What are the trade-offs between different design methodologies. Table design issues. ect.

Thanks