Design Question - Company, Clients, Branches, Departments

Question

Design Question - Company, Clients, Branches, Departments

netpicker9

Mr or Mrs. 500

Points: 559
More actions
December 8, 2010 at 7:37 pm

#228311

Hi,
Can any one please let me know how design tables below,
1. Company
2. Client
3. Branch
4. Departments
Points:
a. Some companies do not have any branches and just departments
b. If company happen have any branch, do I need an entry in branch table for corporate office?
c. Is it better to use Branch, Departments tables for Company & Client tables?
I know this is basic but, I need your help!
Thanks

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Ron McCullough SSC Guru Points: 63877 More actions · Answer 1

What you need to do is to develope an overall requirements document specifying what you management expects to use the database for.

a. What data do people need/want to view

b. How is data collected.

and on and on

Once you have a requirements document finished and reviewed and approved by your managemnt, Then you can concern yourself about individual tables, how they are linked together using foreing keys, etc etc.

If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read[/url]
Before posting a performance problem please read[/url]

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 2

netpicker9 (12/8/2010)
Can any one please let me know how design tables below,
1. Company
2. Client
3. Branch
4. Departments
Points:
a. Some companies do not have any branches and just departments
b. If company happen have any branch, do I need an entry in branch table for corporate office?
c. Is it better to use Branch, Departments tables for Company & Client tables?
I know this is basic but, I need your help!

I assume this is not being developed for a specific company but it is intended to be used to serve multiple companies you don't even know yet - is that a correct assumption?

If that's the case I'll make an executive decision and say "all companies have at least one branch - which is the company's headquarter"

Then, for a three "branches" company your database will show four e.g. headquarter plus three non-headquarters branches.

Hope this helps.

_____________________________________
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.

Toby Harman SSCarpal Tunnel Points: 4168 More actions · Answer 3

Collapse the structure to a single table and use a HIERARCHYID.

That way you can define a flexible heirarchy in this table and attach to specific points.

harinerella Mr or Mrs. 500 Points: 548 More actions · Answer 4

An ER diagram will help more to understand the relation ships

harinerella Mr or Mrs. 500 Points: 548 More actions · Answer 5

An ER diagram will help more to understand the relationships