Home > SSW Standards > SSW Rules > Rules To Better SQL Server Databases
Frequently when I'm reviewing a client's SQL Server database design, the in-house
developers tell me that "it's a bit of a dog's breakfast." 10 different developers
have been working on it for a few years so a lot of the basic defaults have not
been changed. Here are some of the typical things that all SQL Server DBAs and Database
developers will know. These rules are above and beyond the most basic textbook
recommendations of:
- Ensuring your databases are Normalized and in 3rd Normal Form
- Making sure you have primary keys, foreign keys and simple indexes to improve performance
- Making sure you Back up regularly
- Basic Naming conventions (see some of our
object naming conventions)
- Minimizing resultset sizes and data over the wire
Now I don't see a purpose in rewriting applications that work. But - I do see the
value in making an application standardised. We all KNOW that standards are a good
thing, it's time we were all brave enough to be strict. Here are the standards that
we follow...
Do you agree with them all? Are we missing some? Email us your tips, thoughts or
arguments.
Let us know what you think.
|
*** Update *** Instead of manually implementing these rules, use
SSW SQL Auditor to automatically implement many of them for you.
Download it and give it a go.
|