#Download northwind.mdb sample database update#
#Download northwind.mdb sample database professional#

Hopefully, VS 2008 SP1 will contain the fix for LINQ to SQL's O/R Designer to enable visual design with SSCE v3.5 databases. The only difference from the SQL Server version is that the Order Details table is named Order_Details. The Employees and Categories tables include the original bitmaps. So I modified the InstNwnd.sql script from the SQL Server 2000 Sample Databases installer to create with SSCE v3.5 the original eight Northwind tables with the same indexes, as well identical constraint and column names as the SQL Server 2005 version.

#Download northwind.mdb sample database professional#

I needed compatible SQL Server 2005+ and SSCE v3.5 Northwind versions for my forthcoming Professional ADO.NET 3.5 LINQ and Entity Framework book for WROX/Wiley. However, you can't use the same Entity SQL or T-SQL test queries with Northwind.sdf and Northwind.mdf. You can delete and replace the offending constraint names in VS 2008's Server/Database Explorer (but not in SQL Server 2008's Management Studio). The EDM Designer replaces spaces in column names with underscores but not foreign-key constraints.

My problem with SP1 showing 27 'ghost errors' for a simple EDM from Northwind via SQL Server Express doesn't reproduce today.

#Download northwind.mdb sample database update#

Update : VS 2008 SP1 Beta appears to solve the 'ghost error' problem with spaces in FKConstraint names.

I'm also seeing 'ghost' or 'fake' errors when creating sample models from plain old Northwind (PONW) tables with ADO.NET Entity Framework SP1 Beta. The Error List window now lists fake errors for all of our subtypes that are children of abstract entities with a message similar to вЂњEntity types B, C, D are mapped to table A without discriminating conditions on all mappings to the table.вЂќ Update : In his New Entity Framework designer bugs in SP1 beta of May 14, 2008, Ryan Hauert finds the following bug most frustrating:

Update : The compile-time errors aren't fatal and disappear when you compile and run the project. For example, when you use the original Northwind.sdf sample database in an ADO.NET Entity Framework project, the two Order DetailsFK0# constraints each raise 11 compile-time errors for the Northwind.ssdl file. It might be acceptable to include spaces in column and constraint names in Bangalore but it's not considered a good database design practice in western countries. As far as I can determine, this is the first sample database from Microsoft since Access 2.0's Northwind.mdb to have spaces in column names. Microsoft India's Northwind.sdf sample database file for SQL Server Compact (SSCE) v3.5 that ships with Visual Studio 2008 has a defect: Its column names and two foreign-key constraints (Order DetailsFK00 and Order DetailsFK01) contain spaces.