DO’S:
1)Do watch servers closely and be alerted when processes are slowing down. When you see a problem, do react as quickly as possible.
2)Do track usage by end users. You can't test end user usage in the test environment, so keep close tabs on them after deployment.
3)Do focus on top-level business needs, rather than furthering your own technical aptitude.
4)Do beware of Deadlocks and timeouts.
5)Do learn how to read a Query Execution Plan.
6)Do employ key management practices, such as automated monitoring. That way, relying on specific manual processes to fix problems is not necessary.
7)Do Maintain your Expertise.
8)Do get in the right frame of mind.You don't need to focus your efforts on writing code to solve every problem. If you do, "there are hundreds of things you they will need to write,". Instead, focus on implementing and administering management products.
9)Do implement good rollout processes. Once testing is complete, make sure the production center matches the test environment.
10)Do normalize your tables.
DONT’S:
1)Don't rush in applying changes to the database without reviewing/testing first.
2)Don't Waste Time Re-Organizing Your Databases
2)Don't Use temporary tables.
3)Don't Leave Your Database Open To Attack
4)Don't implement something that has never been tested.
5)Don't rely on gui tools to accomplish any task. Great DBAs can endure the SQL queries to get the answer done.
6)Don't create an irreversible change on the server.
7)Don’t wait until you have to restore to validate your backup. Validate your backups once backups are taken.
8)Don't Use Common Extensions For Your Database File Names.
9)Don't Forget to Document Everything
10)Do Not Use tools You are Not Licensed For.
