Advice for Linking DB's

Johnny Drama

In need of beer...
Local time
Today, 15:21
Joined
Dec 12, 2008
Messages
211
Hello all,

I have two DB's: One that holds reports, the report writer, and other details, and a second DB that hold issues that are associated with the reports, who owns the issue, etc. These were built separately and before my time, and it appears it was done this way because they were trying to segregate who could see what in each DB, although there is a common thread (a report may have a number of issues associated with it).

I'm trying to figure out if it's easier to try and merge the two DB's, which I think will end in disaster, or just somehow link the two DB's together. I don't know if this is possible or how I would go about doing it if it is.

Any advice? Thanks in advance for any help/thoughts on this matter.
 
What would be the reason for changing status quo? Perfecting an existing working set-up gives a nice warm feeling, but at an effort to be weighed against the gains. What are the gains?
 
At present there's a disconnect between the reports and the issues within the reports. DB1 contains the high level report information while DB2 contains the issues associated with the reports in DB1, but they are not tied together. Tying them together will allow for better reporting on reports and the associated issues. (I know - that's a lot of reporting. **sigh**)
 

Users who are viewing this thread

Back
Top Bottom