Reg the design approach for the setting of Headquater and branch Databases

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

gaurav - 28 Oct 2004 04:09 GMT

hi

I have one employee table in the db but the requirement is that the
employee of one branch can work for other branch ... but the details
of the emoployee is present in there respective db...

Now the requirement is that how to handle the details of the employees
while reporting and there task schedule for the day.... i.e the
maximum no of hrs in a day is 10 ... so he can work for 5 hrs for one
branch and 5 hrs for other branch..

I am implementing the same in MS SQL SERVER 2000 and ASP.NET...

Can u tell me ASAP

With Thanks

Gaurav

Reply to this Message

John - 28 Oct 2004 08:20 GMT

> hi
>
[quoted text clipped - 14 lines]
>
> Gaurav

If you are trying to use 2 databases to achieve this, you will end up
with an awful mess. The options (as I see it) are:
a) Have one centralised database for the whole organisation
b) Have one 'head office' database, and further databases for each
branch. You will need to do some quite detailed programming if you go
with this option to make sure that there are no inconsistencies between
the head office and branch systems. A good clean design with appropriate
delegation of responsibility is important.

I don't know anything about ASP.NET so can't advise whether this is
feasible.

John

Reply to this Message

Alan - 28 Oct 2004 11:32 GMT

> hi
>
[quoted text clipped - 14 lines]
>
> Gaurav

Quite an interesting assignment, usually given with slightly different
requirements in most textbooks. Here's some hints. M:N. HR data, project
data.

Reply to this Message