The first, as mentioned from Technet recently, is to execute the following parameter details on any SQL Server installation (I tested back to 2000), by run the following command.

sql server optimisation, sql server database management, sql discussions, help, clusters, backups, expansion, usefull tools, mcitp certification, server management, meilleures pratiques sql server, best practices.disaster recovery, deployment management, mirroring best practices and high availability, database security best practices
Free E-Book on SQL Server 2008 R2
Ross Mistry and Stacia Misner have done a wonderful job on this free e-book
You can download the full ebook in XPS format here and in PDF format here.
The book contains 10 chapters and 216 pages:
PART I Database Administration
CHAPTER 1 SQL Server 2008 R2 Editions and Enhancements 3
CHAPTER 2 Multi-Server Administration 21
CHAPTER 3 Data-Tier Applications 41
CHAPTER 4 High Availability and Virtualization Enhancements 63
CHAPTER 5 Consolidation and Monitoring 85
PART II Business Intelligence Development
CHAPTER 6 Scalable Data Warehousing 109
CHAPTER 7 Master Data Services 125
CHAPTER 8 Complex Event Processing with StreamInsight 145
CHAPTER 9 Reporting Services Enhancements 165
CHAPTER 10 Self-Service Analysis with PowerPivot 189
Recently, we found out that HP Data Protector had an update, and I took for granted that this update would make the product more compatible with SQL Server 2008 - but it still doesn't support SQL Server 2008 without installing the Backwards Compatibility Pack from SQL Server 2005.
Not entirely such a pain, but just be aware, HPDP fans, that this warning message 'SQL DMO Component is not available which will cause MS SQL Integration to fail' really means to say you should download the SQL Server 2005 Backwards Compatibility Pack (SQLServer2005_BC_X). If you read the fine print of their Support Manual, you`ll notice on page twelve, point seven, that the SQL DMO download is required.
If you haven't installed the Backwards Compatibilty Pack first, then when using HP Data Protector with SQL Server 2008, you will see this error (HR 0x80040154] Class not registered):
Or notice this error in your Debug.txt (set this in properties) in your Sysroot\Program Files\Omniback folder:
25/03/2010 11:27:48 AM OB2BAR_Main.796.2948 ["integ/sql_7/sql7_dmo.cpp /main/hsl_dp61/hsl_hpit2_2/1":288] A.06.11 b243
[SQL7_Login] Failed creating object instance. Err code: -2147221164, REGDB_E_CLASSNOTREG
Function trace (currentLevel=3):
Level 3: SQL7_Login()
Level 2: SQL7_CheckConfig()
Level 1: SQL7_Config()
Level 0: main()
When Installing the SQL Server 2005 Backwards compatibility Setup, you only need the SQL DMO object components for HP Data Protector to work correctly with SQL Server 2008.