Hi Guys,
i want to create relational database using Access.
In my model i would like to focus first on creating main relationships and later, when you will understand model - i would like to go further.
I have Topology information (topology is a system), Customer, Workload (Topo1 from Topologies tab can divide into Workload1 and Workload2, but this is not always), and server info.
This is a configuration tool.
Customer is choosing topology (system) and specific server assigned to it.
When Topo1 is choosen, then can be also choosen one workload for it. (It is distinction for OLAP or OLTP but this could not be required).
Server have bunch of characteristics. One of them is infrastructure.
Customer1 and Customer2 has to have server with Infrastructure1, but Customer3 has to have possibility to choose only servers on Infrastructure2.
How properly design database here?
Maybe junction table it is not necessary?
My thinking here is:
Customers can have choose bunch of topologies/systems. Like Topo1, Topo2 and Topo3. For each of them we can have a lot of different servers.
We should also have possiblity to in easily way change server assignment to different Customer, or different topology or both of them.
Best,
Jacek
i want to create relational database using Access.
In my model i would like to focus first on creating main relationships and later, when you will understand model - i would like to go further.
I have Topology information (topology is a system), Customer, Workload (Topo1 from Topologies tab can divide into Workload1 and Workload2, but this is not always), and server info.
This is a configuration tool.
Customer is choosing topology (system) and specific server assigned to it.
When Topo1 is choosen, then can be also choosen one workload for it. (It is distinction for OLAP or OLTP but this could not be required).
Server have bunch of characteristics. One of them is infrastructure.
Customer1 and Customer2 has to have server with Infrastructure1, but Customer3 has to have possibility to choose only servers on Infrastructure2.
How properly design database here?
Maybe junction table it is not necessary?
My thinking here is:
Customers can have choose bunch of topologies/systems. Like Topo1, Topo2 and Topo3. For each of them we can have a lot of different servers.
We should also have possiblity to in easily way change server assignment to different Customer, or different topology or both of them.
Best,
Jacek
Attachments
Last edited:
