July 15, 2010 at 4:33 pm
Hello
I am a fresher and I am involved in designing and developing a database.
July 16, 2010 at 6:44 am
I guess the answer is it depends. Is this an OLAP or OLTP database? Warehouse? I would try to eliminate duplciation of data where possible, but that's a general guideline. I like using surrogate keys as opposed to huge composite natural keys, but again that depends. Is every field in the table part of the key? How many fields are needed to make up the key? etc.. As you say, you are new at this, so I would ask if there a senior person in your shop you can look to for guidance?
For better, quicker answers, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 16, 2010 at 11:14 am
My personal preference is to use natural keys when possible when modeling general purpose or OLTP databases - while doing dimensional modeling I recognize the benefits of relying on surrogate keys when needed.
In regards to normalization and since list of tables looks like a general purpose or OLTP database I would strongly suggest to go for 3NF.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply