Ok, I have a rather large relational database I'm building and have run into a problem relating tables to each other. I need to relate an ID in one table to several other tables. And this occurs several times. I'm going to give a fictitious example to try and reflect what I'm doing.
I have a large number of assets which are all very unique with their own properties. For example, Apples, Oranges, Bananas, and Grapes. Tied to each of these are Images and Reports. So I have a table for each asset, which each has an ID number which is a GUID. The Images table houses all the images, the Reports table houses all the reports.
Now what I'm looking for is this. What is the best practice for linking the Images and Reports back to the individual asset?
Right now what I've setup is an AssetID in both the Images and Reports table which points to the ID number of the asset owner. The problem is I have no idea which asset table this ID comes from, it could be from Apples, Oranges, Bananas or Grapes. With Images this isn't that big of a deal as I only lookup images coming from the Asset-to-the-Image. For reports this is a problem though. For reports I have to go from Reports-to-Assets. The report will vary depending on whether it's for an Apple, Orange, Banana, or Grape.
I need to be able to do queries on the reports table and then generate reports based on the asset they come from. Obviously I can setup a stored procedure to loop through the asset tables and find the correct asset, etc. But is there a better way to do this?
My understanding is that a GUID is always unique, so using one ID column to reference multiple table IDs shouldn't be a problem as far as unique IDs are concerned.
I could setup a ReportToAsset table that contains ReportID, AssetID, AssetType (the name of the asset table, Apple, Orange, etc.). To me though this seems just as precarious as what I have setup now... unless there is a way to setup a hard relationship between the asset tables and the ReportsToAssets table. Is this possible?
So, database experts, what's the best way to solve this? I'm looking for a solution that can directly relate the record to the proper table. The solution could be in many forms, an altered table structure, or with a fancy SQL query that figures out the correct relationship.
If I were to delete a report I cannot currently setup a relationship to automatically cascade and delete the asset associated with that report. I would have to do it manually with code. What is the standard practice in this sort of information structure?