September 2005 Blog Posts

  • 10 Common Design Mistakes

    1) No logical model Obvious isn’t it?  But I can almost guarantee that everyone has started a DB project without one at some stage.  You are lucky if you see an ERD and should buy a Lotto ticket if you see a Functional Dependency analysis.  As an example, my current project’s schema can be broken into 7 functional areas.  I produced ERDs and FDs for 5 of these areas but ignored the other 2.  Despite changing requirements, the “planned” 5 areas remain almost untouched, while the “unplanned” schemas have undergone countless re-writes.  By the way, the 5 “planned” areas make up...

  • How to be a good DBA

    Love: A good DBA loves his data and DBMS.  And like any good relationship, they communicate with each other SQL Server: “What a day! “ DBA: “What happened? “ SQL Server: “Some guy does a batch load and before I have time to update the stats, someone else decides to run the end of month report.  It hurt.  Can you run a "defrag” on me please?” DBA: “Of course I can. Do you have the credentials of the user who ran the end of month report? SQL Server: “Yeah, it’s in the trace table in the admin database. DBA:...