Hello,

 When I reverse engineered a SQL Server 2008 DB, I got a bunch of 'Unresolvable Warning' on relationships.  When I look at the relationship in SQL Server Management Studio, all looks good.  Both columns on each side of the simple relationship are there.  Any ideas what else might be causing this or something I could try to correct this?

Warning: Relationship EntityAnswers.FK_EntityAnswers_Field unresolvable. Parent Key Field.2 is not part of the model.
Warning: Relationship Calendar.FK_Calendar_GenericScope unresolvable. Parent Key GenericScope.2 is not part of the model.
Warning: Relationship ResourceCategory_EntityType.FK_ResourceCategory_EntityType_EntityType unresolvable. Parent Key EntityType.2 is not part of the model.
Warning: Relationship Ad_EntityTypes.FK_Ad_EntityTypes_Ad_EntityTypes unresolvable. Parent Key EntityType.2 is not part of the model.
Warning: Relationship GroupEntityTypes.FK_GroupEntityTypes_EntityTypes unresolvable. Parent Key EntityType.2 is not part of the model.
Warning: Relationship Resource_Categories.FK_Resource_Categories_ResourceCategoryScope unresolvable. Parent Key GenericScope.2 is not part of the model.
Warning: Relationship Resource.FK_Resource_ResourceAttachmentType unresolvable. Parent Key ResourceAttachmentType.2 is not part of the model.
Warning: Relationship EntityTypeFieldVisibility.FK_EntityTypeFieldVisibility_Field unresolvable. Parent Key Field.2 is not part of the model.
Warning: Relationship ForumCategory.FK_ForumCategory_GenericScope unresolvable. Parent Key GenericScope.2 is not part of the model.

Thank you,

 Bill Devine

First, are you sure this is a SQL Server 2008 database?  If it is a 2005 database, then select that as the target and convert to 2008 once its RE'd.

---

Scott Reynolds
Technical Support Engineer
ModelRight, Inc.
www.modelright.com
p: (609) 423-9296
f: (866) 812-3742

Yes, I'm positive it's on a 2008 SQL Server.  The actual DB used to be in SQL Server 2005 but was brought over via detach/reattach from SQL Server 2005 to SQL Server 2008.  Should I still try importing as a SQL Server 2005 and then converting to 2008?

Yes, please try it as 2005.  I'm not sure if an attach is the same thing as a real 2008 database.

---

Scott Reynolds
Technical Support Engineer
ModelRight, Inc.
www.modelright.com
p: (609) 423-9296
f: (866) 812-3742

I tried it as 2005 and got the same results.  I'm going to try and wipe out the relationships that MR isn't picking up and re-create them via MR.  There aren't that many of them that I'm getting this warning on.

 Thank you for the quick responses yesterday!

 Bill

Ok.  We'll try to reproduce with a similar setup.  We would like to fix this if its an issue.

---

Scott Reynolds
Technical Support Engineer
ModelRight, Inc.
www.modelright.com
p: (609) 423-9296
f: (866) 812-3742

Just an update:

I believe all those 'unresolvable' warnings were a result of bad database design.  The Parent side of the relationships I was receiving the warnings on were not defined as a PK or Unique.  A couple didn't have any primary/unique/index defined on the column and the others where just defined as an index.

 Thanks again,

 Bill

Hi Bill,

Thanks for the info.  I wonder how such a relation can even be defined?

---

Scott Reynolds
Technical Support Engineer
ModelRight, Inc.
www.modelright.com
p: (609) 423-9296
f: (866) 812-3742

Yeah, good question!  I was wondering the same.  This database has had way too many developer's hands in it. Some with extensive SQL Server DB knowledge and some more on the novice side.  I'm finally just trying to get the whole thing under control because it's a significant pain point.  Especially when preparing for a new version release and having to migrate current customer databases to the 'latest and greatest'.  I think ModelRight is going to help me out a great deal here and help me keep my sanity. :)

 Bill