1) People to use consistent naming conventions - If you're using camel case, stick with it. If you're using Pascal case (the first letter of every word Capitalized), stick with it. If you're using underscores ( _ ) between names, stick with it. If you're organizing stored procedures by using titles that start with a verb( GET) and a noun or adjective (Person) stick with it.
2) Everyone at MS should have a Thesaurus (see if you can count how many different ways the word "Schema" is used in SQL 2005.
3) Snow storms would not hit at precisely the time at which I'm trying to fly home after some job on the east coast.
4) Database developers would use SQL Server Schemas for security, or use object level grants, but not mix the two
5) Reporting Services administrators would backup up their encryption key.
6) Analysis Services designers would not use Data Mining unless they can clearly explain what the Naive Baysian mining algorithm is (I mean write the formula down)
7) DBAs would actually test the backups they have (please for the love of all that is normalized in this world!)
8) Database designers would start with a logical, noramlized (3rd form will do) before even considering denormalizing a database.
9) When writing functions or stored procedures, no one would use EXECUTE AS unless they can explain exactly what SELF, CALLER and OWNER mean. ( and hopefully not use it all)
10) A Red-Rider BB gun to hold off the miscreants of Black Bart.