Entity Framework v2 does not support sql 2000?

Question

I installed beta version 2 of Visual Studio 2010 today. I went to check out the new entity infrastructure stuff (to check if my "problems" from v1 were fixed.).

I started adding a new connection string, but when I entered my information for sql 2000, she said that "this version of the server is not supported. You must have SQL Server 2005 or later." They refused support for Sql Server 2000 in v2 entity structure?

Answer 1

They sent a call to Microsoft support, and they answered:

Entity Framework v2 does not support SQL 2000

Here is the answer:

Thanks for posting this bug. Unfortunately, a business decision was made to no longer support SQL Server 2000 in this scenario.

Thus, there is no support for SQL 2000 within entity v2 in .net 4.0

Answer 2

I have a job that has not yet been disqualified.

How to use Entity Framework 4 with Visual Studio 2010 and SQL Server 2000

Answer 3

What happens if you create a model with VS 2008 and then convert this project to VS2010 and change the target structure to .Net 4.0?

Answer 4

In fact, EF 4.0 supports SQL Server 2000. This is a Database Explorer in Visual Studio 2010 that does not support SQL Server 2000. To work around this, do not use the Database Explorer. Instead, simply create an empty model, then overwrite the connection string in the configuration file using the SQL Server 2000 connection string. Then you can use the "Update Model from Database" in EF Designer to add your objects.

Answer 5

Hope this is just for beta, as the documentation still speaks of 2000 support. Http://msdn.microsoft.com/en-us/library/bb896309(VS.100).aspx

You might want to send it for connection (see FEEDBACK in the Visual STudio IDE).

- added - I just want to confirm that this happens in the EDM wizard when you point to a specific database. True?

Julia Lerman

Answer 6

This is not just an EF that does not support SQL Server 2000. In Visual Studio 2010, Beta 2 Server Explorer does not even allow you to add a data connection to SQL Server 2000.

It is strange that my DN Framework v1.1 code, which uses SqlClient when porting to DN Framework v4, still works fine.

I can only hope that they will add MSSQL 2k support back to the time of its release.