August 3, 2008 at 6:41 am
Hi,
I've been looking a lot at data modeling of late and I must say, it is difficult to create a database out of the structure. Sometimes, the tables are too many. At time, the nested nature of the entities in the diagram makes it difficult to know what goes where.
Let's look at the structure below
Party
--Person
--Employee
--Organization (recursive)
- Employment (joins organization with Employee or another organization)
etc, etc
Sometime, there is even the statement that the parent of entity A is either entity B or entity C but not both.
1. Can I be directed as to how to create databases out of these models?
2. Is implementing the models as they are really the best thing?
Thank you.
August 4, 2008 at 3:09 am
Which data modeling tool are you using? Use any good tool like ERWIN and use option of forward engineering to get your database creation script. The reverse option is available too ..
[font="Comic Sans MS"]--
Sabya[/font]
August 4, 2008 at 12:11 pm
The database forms the foundation of most applications. For this reason, your primary goals in creating a good database model or design must be to achieve data integrity, scalability, and performance. Reasonable normalization can help you in this regard. I suggest you search SQL BOL or the web for topics dealing with the benefits of normalization.
August 4, 2008 at 6:42 pm
I've have been normalizing my data a lot - almost always to the 3rd normal form. It is just that when I look at the model I saw with so many entities and sub entities, it appears that the tables will be a lot. With this, I do not know if I am on the right track.
sabyasachi.mukherjee:
I'm not using any data modeling tool. I'm checking out Erwin though.
Thank you.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply