I believe each topic needs its own authorative source. There is no one size fits all when it comes to SQL practice and/or development. Everywhere you look you find good arguments for doing things one way or another...........the best source is the one that allows a DBA to find the best practices for performance, stability and usability given his own setup. To ignore those conditions specific to that DBA's own business/data environment is asking for headaches and do overs.

Any DBA will attest to this: the best list for anyone in our world is more about what NOT to do than best practices ;). Start that list with......take a backup even when you dont think you need one.