M
Max Metral
I remember having attempted this before but it was a miserable failure. Now
I simply can't figure out how it was meant to work, and there is little or
no documentation that I could find about it.
So, I have a database with say 20 tables. 10 are related to concept A, and
10 to concept B. (The real number is larger, and that's why one document
won't do). So I want to create a database model project. I want to have
two source documents, for A and B. Tables in A reference tables in B.
(There are C and D and E, but first things first). Assuming these tables
and relationships exist in SQL server already, how should I go about
creating them and making the cross-document references work in the context
of the database project? I've tried external tables/columns with no luck.
I've tried leaving out the relationships in the source models and reverse
engineering in the db model, no luck.
What is the defined process for reverse engineering a database like this?
I simply can't figure out how it was meant to work, and there is little or
no documentation that I could find about it.
So, I have a database with say 20 tables. 10 are related to concept A, and
10 to concept B. (The real number is larger, and that's why one document
won't do). So I want to create a database model project. I want to have
two source documents, for A and B. Tables in A reference tables in B.
(There are C and D and E, but first things first). Assuming these tables
and relationships exist in SQL server already, how should I go about
creating them and making the cross-document references work in the context
of the database project? I've tried external tables/columns with no luck.
I've tried leaving out the relationships in the source models and reverse
engineering in the db model, no luck.
What is the defined process for reverse engineering a database like this?