views:

868

answers:

4

Is there a way to use the SQL Model (dbml) builder in VS2010 using SQLServer2000? It works fine in VSExpress2008 + VS2008 but throws an "Upgrade SQL to 2005" error in VS2010 which seems a tad unreasonable.

A: 

Reading here (Goto SQL Server 2000 Support near the bottom) support is very limited for LINQ-SQL, which means you might have to consider upgrading if you wish to use LINQ-SQL

kevchadders
the DBML thing works fine, I tend to use it more for dropping Stored procs in as it works pretty well for that.
Chris M
To clarify that, DBML Works fine in VS08 with SQL2000 its just VS2010 that seems to opt out. Ideally of course work would just update their Database ;o)
Chris M
I don't think SQL server 2000 support is "very limited". Works great in my experience, the only problem here is that VS2010 dropped it.
Eduardo Molteni
+1  A: 

Here's a couple of options:

  1. Create a 2008 project that's solely for updating the DBML file. Jump into that project when you want to manipulate the DBML file using the designer.

  2. Update the DBML directly (ick!).

MadMoai
I went for option 3. move everything over to NHibernate and stop relying on VS as much, being at the mercy of Microsofts sales push isn't a good place to be :o)
Chris M
You don't need to create a project. You can just open the DBML file with VS2008, update and save.
Eduardo Molteni
+1  A: 

I've just had this same problem and overcame it by creating the DBML file in VS2008 and then just copying it into my VS2010 project.

First I tried creating it using SQLmetal from a VS2010 prompt but the connection information doesn't get persisted then of course you cannot add the connection from the dbml editor as it wont hook up to SQL2000.

Hope this helps.

Mechamonkey
A: 

I was also having this problem when I was trying to add a data connection via the server explorer in VS 2010- it says that it only supports connections w/ MS SQL 2005 or greater. I was able to get it to connect with my SQL Server 2000 db by adding the connection by choosing and selecting ".NET Framework Data Provider for OLE DB" as the data source and for the OLE DB Provider ddl choosing "SQL Native Client", then entering the server the db resides on, the security, and the db name.

jg100309