DenkzeitWiki

BeingDBA

• Presentation: What I Wish Developers Knew About SQL Server
  
• Recommended SQL Books
  
• http://www.thinkgeek.com/tshirts/coder/595d/

SELECT * FROM users WHERE clue > 0

0 rows returned

• Intelligent Database Management
  
  
• Database Apprenticeship (apprenticeship, apprentice, master, craft)

Best Practices

• Rules to Better SQL Server Databases
  • lots of rules
• Ten of the Biggest Mistakes Developers Make With Databases
• 25 SQL Commandments
  • deep wisdom
  
  
• SQL Server Database Coding Conventions, Best Practices, and Programming Guidelines
• SQL Server 2000 Best Practices
• http://www.sqlusa.com/bestpractices/
  
• Best SQL Coding Practices ppt
  
• The Data Commandments

• That's right, if you want to do a really professional job of building software you need to extend VersionControl to your database design.
  
  
• SQL ordering
  • usually ordering (if none is given in the SQL-statement) is arbitrary
  • MSSQL has ClusteredIndices

Alter Column

• http://www.nigelrivett.net/SQLAdmin/AlterTableProblems.html
  • May waste space in every row.

Formatting SQL

• http://awads.net/wp/2005/12/12/format-your-sql-the-easy-way/
  • http://www.sqlinform.com/
• http://www.peterbe.com/Pretty-print-SQL-script
• Formatting Your SQL Statement
• Some Simple SQL Rules to Live By

Tipps 'n' tricks

• How to stop execution of your SQL code in a SQL Script

SET NOEXEC ON

Logging

• http://www.highscalability.com/log-everything-all-time

You need a log of all the interesting things that happened in the system. Knowing "func1" was called is of no help. You need to know all the parameters that were passed to the function. You need to know the return value from the function. Along with anything else interesting it did.
...
I can hear many of you saying this is too inefficient. We could never log all that data! That's crazy! No true. I've worked on very sensitive high performance real-time embedded systems where every nanosecond was dear and they still had very high levels of logging, even in driver land. It's in how you do it.
You would be right if you logged everything within the same thread directly to disk. Then you are toast. It won't ever work. So don't do that. [1]

Bad Practices

• Bad practices in sql server
  • ...
  • Use of enterprise manager for data or schema updates.
  • A task to frequently shrink databases.
  • Database access other than by stored procedures. Embedded sql in the client.
  • Application bound to the database structure (application should have no knowledge of tables).
  • Updating primary keys.
  
  
• The Seven Deadly Habits of a DBA ... and how to cure them (toberead)

Fun

• Journey to the Center of the Database (wtf, normalization, fun)