I've got a relatively simple task I'd like to perform but not too sure on the 'correct' way pf creating the database schema.
I'll describe my query in the form of an example.
I have table A that contains a list of Servers
Table B contains a list of Services that could be installed on a server
A simple one to many relationship would be created between the two so that any one server could be hosting one or more services.
Now the part I'm stuck on...
I want to create a third entity that will list services that are dependant on each other. E.g. Active Directory is dependant on DNS. Therefore I'd like an entity that would reference two servers - I'm informed you can only have one foriegn key between two tables.
E.g. I can't have field ServerA relating to Services as well as field ServerB also relating to services.
Is this correct? Is there a better way of designing the database?