Keep Sites Running Smoothly By Avoiding These 10 Common ASP.NET Pitfalls

Straight from msdn magazine:
Keep Sites Running Smoothly By Avoiding These 10 Common ASP.NET Pitfalls -

1. LoadControl and Output Caching
2. Sessions and Output Caching
3. Forms Authentication Ticket Lifetime
4. View State: The Silent Perf Killer
5. SQL Server Session State: Another Perf Killer
6. Uncached Roles
7. Profile Property Serialization
8. Thread Pool Saturation
9. Impersonation and ACL Authorization
10. Don’t Just Trust It—Profile Your Database!

Check this: http://msdn.microsoft.com/msdnmag/issues/06/07/webappfollies/default.aspx

On Demand webcasts...

http://blogs.msdn.com/bimusings/archive/2005/12/13/503110.aspx

The (un)official guide to SQL Reporting Services 2000 & 2005 interop

Do you need Windows server 2003 for SQL 2005 Reporting services? Yes for Server components, and Windows XP for workstation components. Basically for developement and testing purpose XP should be an ideal bet. You do get a designer after all :)

Check this blog for questions surrounding differences between SQL 2000 and SQL 2005 reporting services: http://blogs.msdn.com/bimusings/archive/2005/12/13/503110.aspx