Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Database copy does seem to copy all tables
Message
From
24/05/2010 17:44:40
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
 
 
To
24/05/2010 16:46:23
Kevin Frazier
Strategic Angel Software
Canton, Ohio, United States
General information
Forum:
ASP.NET
Category:
The Mere Mortals .NET Framework
Environment versions
Environment:
ASP.NET
OS:
Windows 7
Network:
Windows 2008 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01465745
Message ID:
01465770
Views:
41
>Yes. I was creating entity framework bizobjects. I am in the process of rewriting portions of an application that currently uses classic business objects. I want to use the entity framework business objects. I was following the jump start, but I was using my database in place of the database from the jumpstart. I did try also use the adventureworks database for testing, but it also errors out. The database is created, but I never compared the databases of the copy with the original for AW. However in my database the copy utility doesn't appear to bring all the table objects over. It could be that it is erroring out. I am using Team Foundation Visual Studio 2008 with SP1 and SQL Server 2008 and Mere Mortals 3.6


Ok, I suspected. The easy answer would be to go to VS2010 and Dot net EF 2.0 but I realize that isn't reasonable. :-)
The step I would take are to first run the copy utility against the Northwind database to verify the copy utility works for you. If that does, then it is probably because of something in your data that just doesn't quite jive with the way the copy utility works. It would be pretty easy to just make your own copy and then remove all the relationships in the copy so you could use it for this purpose.

Remember the only point of this excersize is to get an entity model that doesn't screw with the way the foreign keys work. It was a mis-step in the way MS did that and they have changed it for EF 2.0; a copy would no longer be needed to create your data model. It would take longer to try to figure out why your data doesn't work with the utility than to just create your own copy.

If the copy utiltity does not work with the Northwind database, then something else must be the culprit. Answer could still be the same if you just need a data model so you can move forward.
I hope that helps some.
Tim
Timothy Bryan
Previous
Reply
Map
View

Click here to load this message in the networking platform