This project is read-only.

What version of Sql Server for 3.5 Entity Framework BeerHouse

Nov 27, 2009 at 6:57 PM


Which version(s) of Sql Server can be used for the latest version of the BeerHouse database (i.e the 3.5 Entity Framework version of BeerHouse)

I am using Sql Server 2005 but when i attach to the MDF I get a 655 error ....

 <font size="1">

The database 'TheBeerHouseEF' cannot be opened because it is version 655. This server supports version 611 and earlier. A downgrade path is not supported.



So I am guessing I would need Sql Server 2008

Is this correct - or am i missing something ?



Nov 28, 2009 at 8:02 PM

It is SQL Server "Express" 2008.  The MDF will not attach to any other version that I've tried. Not 2005, not 2008 Developer, only SQL Express 2008.  See post "Attach Database Filed for TheBeerHouseVB" for more on this...


Nov 30, 2009 at 10:58 AM


Don't know about any of you guys but i feel this situation with the supplied mdf file is not good.

I have the 2.0 version of BeerHouse on my machine and i am using sql srvr 2005 with it.

(i also have various other devlopment projects on my machine which i want to keep running)

Assuming that i cannot run sql srvr 2005 and 2008 side by side, I am being left with no option but to dump this book and it's project which would be a pity.

I am in no doubt that there should be a version of the mdf to cover the most widely used version of sql srvr at this point in time (which is not 2008).



Nov 30, 2009 at 4:15 PM

You assumption is wrong.  You can have SQL 2005 and SQL 2008 running side by side.

Nov 30, 2009 at 4:32 PM

Right, Developer version SQL2005 and Developer SQL2008 can live side by side. I have both of these running now. What I'm having trouble with is having Developer SQL2008 and SQL Express 2008 living side by side. If anyone has this working then please state so.

I would prefer to run the DB in Developer SQL2008. Any advise on how to accomplish this? I've tried having someone do a SQL Backup in Express, but the BAK file will not restore to Dev SQL 2008.


Nov 30, 2009 at 5:29 PM
Edited Nov 30, 2009 at 5:31 PM

Just install it under a different name. 

localhost (sql 2005)

Is that not possible?  If not why not just attach the MDF to SQL 2008 Dev and then modify the connection for that server?

metadata=res://*;provider=System.Data.SqlClient;provider connection string=&quot;Data Source=.;Initial Catalog=TheBeerHouseVB;Integrated Security=True;MultipleActiveResultSets=True&quot;
Nov 30, 2009 at 5:39 PM

Yes well that was my plan, install Express under a different instance, but the SQLExpress installer wants to 'replace' the version of SQL 2008 previously installed, or 'repair' it... The install wizard donesn't seem to allow a separate install - at least, not that I've been able to see. 

Regarding the 'attach' - you're not able to attach the MDF to SQL 2008 Dev. It returns an error stating that the DB version is 655, and SQL Dev only works with DB's to version 639...

I should try again to get SQL Express 2008 installed as another instance, I was hoping to find confirmation that this is possible before I spend a lot of time on it.

Nov 30, 2009 at 6:34 PM

Are you sure you are using the latest service pack of SQL 2008? 

Nov 30, 2009 at 6:51 PM

It's version 10.0.1075.23 ((SQL_PreRelease).071108-1357 ) with 2008 SP1 installed.

Nov 30, 2009 at 8:40 PM

SQL_PreRelease?  That could be your issue.

Nov 30, 2009 at 10:51 PM

Actually no. I just spoke with an old collegue who has SQL2000, SQL2005 Dev, SQL2005 Express, SQL2008 Dev (pre_release), and SQL2008 Express all running on the same machine as different named instances. So, there must be something I've been doing wrong when  trying to get the SQL2008 Express installed on my machine. Moreover, he indicated that he attached the BH database MDF through Visual Studio 2008's data connection process, and not through the SQL management console. I'm not sure that has anything to do with it...

I'm going to work on the SQLExp 2008 install and try to get that working... I'll post my findings and results soon.

Dec 10, 2009 at 11:40 AM

The book and therefor the Entity Model was created against SQL 2008. So you must have that running for the model to work. I heard there is a way to mannual tweak the model's XML to change it to use SQL 2005. Once I have some free time to verify that I will post a blog on doing that.

The other thing I am thinking as I read this is you need to change your connection string to point to the correct instance of SQL if you are running multiple instances.

Apr 8, 2012 at 12:13 AM

What connection string would I use for a remote sql 2008 server not sql2008 express?