To select the data using a common key you can create a view that includes a three-part qualifier: database-schema-table. Below I assume that each personnel entry has a CompanyID field that ties them together and that dbo is the schema. If such a field doesn't exist, you will need to create and populate one:
CREATE VIEW vCompanyPersonnel
AS
SELECT * FROM tblCompany t1
JOIN dbPersonnel.dbo.tblPersonnel
t2 ON t1.ID = t2.CompanyID
Similarly, in order to make updates to either table and maintain referential integrity, you will need to create stored procedures and only allow applications to update the data using those procs (which is a best practice, anyway). You should also make sure that the CompanyID field in the personnel table does not allow null values. Some procs to consider:
- Add Personnel: require a CustomerID input parameter and make sure it exists in the Company table. If not, RAISERROR.
- Delete/Deactivate Customer: also delete/deactivate all associated personnel, preferably having the whole process wrapped in a transaction (all or nothing).