There are trade-offs either way.
Single File advantages
Moving/renaming single file solution rarely affects database function.
Single set of accounts, passwords and privilege sets can be maintained for the entire system. (With multiple files, you have to set up identical account name and passwords in each file).
Multiple file advantages
If you have to deploy an update that modifies just one table, you have a much simpler job of importing existing data into just a portion of your system instead of importing data from all your tables as you do with a single file solution.
What are the details of the training you need to track? If someone was trained on two devices, would you enter their personal details twice in the training table?
The person is assigned to the course and the device is assigned to the course. There can be multiple devices to any one course.
Right now I have it broken out into two seperate databases: the training database has the following tables:
And then I have it pulling Device from the Devicetbl in the device database.
In the Device database I have the following tables:
Any suggestions on changes or if It looks like i have designed incorrectly please let me know. The tables with the _ between two words are join tables.
Thank you Again.