11

I recently installed Visual Studio 2010 and SQL Server 2012 on a Windows Server 2008 R2 machine - (including all updates/Service Packs).

When attempting to work on a SQL Server database from within Visual Studio, VS throws the following error:

This server version is not supported. Only servers up to Microsoft SQL Server 2008 are supported

I recall getting this same error a while back (on a different computer) when I updated a SQL Server 2008 instance to SQL Server 2008 R2. The fix, back then, was to install (or reinstall) Visual Studio 2010 SP1.

Now that I'm receiving this error again (on a new computer), I thought it reasonable to reinstall VS SP1 just like I did a while back. However, doing so did not fix the problem.

It appears as though Visual Studio may need another update to support SQL Server 2012 instances.

For clarity, here are the steps that I did to produce the error: (using VS 2010sp1 and SQL2012)

  1. Using VS, create a Windows Forms application
  2. Right-click the project and choose, Add > New Item
  3. Select "Service-based Database"
  4. Cancel out of the "Data Source Configuration Wizard"
  5. A Database will appear under your Project in Solution Explorer. Double-click the new database
  6. The Database will be added to Server Explorer's list of Data Connections
  7. In Server Explorer, open the database, right-click the Tables directory, then select "Add New Table"
  8. The error "This server version is not supported...." is thrown

Screenshots for whatever its worth.. enter image description here enter image description here

My question is, is there a fix for this? If so, what is it?

Jed
  • 10,649
  • 19
  • 81
  • 125

6 Answers6

6

Maybe get SQL Server Data Tools, which work with SQL Server 2012? I believe there are some good tutorials and other materials in the Developer Training Kit. I don't think there are any tricks yet to make an older version of Visual Studio / Data Dude compatible with SQL Server 2012.

Aaron Bertrand
  • 272,866
  • 37
  • 466
  • 490
2

Following MSDN blog link discusses about the issue that you are facing with local SQL Server database instance in Visual Studio 2010.

Using LocalDB in Visual Studio 2010

  • +1 this is a good pointer. However while this allows VS to connect to (localdb) I don't know that this will make Visual Studio 2010 aware of new SQL Server syntax, able to use the proper compiler/parser/language service, etc., or whether it will also work on traditional instances (e.g. does the workaround work only because it's (localdb))? If any of these don't have the right answer, then the solution might be to use the version of VS that was written to accommodate SQL Server 2012... – Aaron Bertrand Apr 23 '12 at 18:14
2

My problem was that I couldn't get VS2012 to work right with SQL Server 2012. I installed the latter product first, but after installing VS2012 and attempting to open an existing project, my existing data file just would not work. I know the software is supposed to automatically take you through a wizard to update your database in the project, but that didn't happen, and I couldn't find a way to make it happen. I'm on the point now of getting rid of SQL Server 2012 and going back to 2008. I'd rather use the most current releases, but I can't spend any more time on configuration issues.

user382459
  • 141
  • 2
  • 3
0

I tried reinstalling the SSDT as well, but kept getting the same error you mentioned Jed, this seemed to let me get around the error message:

http://forums.asp.net/t/1721552.aspx/1?Working+with+Denali+SQLEXPRESS+in+VS+11+Database+issue

crosan
  • 486
  • 4
  • 13
0

This error could also occur if you use the wrong provider. A recently came across the "This server version is not supported...." error and after changing the provider from sqlClient Data Provider to SQL Server Native Client 11.0 in the connection string for the Data Source configuration the problem was solved.

Samuel Osei-Tutu
  • 1
0

For me, the error arises whenever I try creating a new database. So after unsuccessfully attempting all methods advised, I bypassed the error by clicking on "Add connection" and putting my server name in the dialog box. After adding the non-existent database name, it notifies that it can't find such database and asks whether to create it. Voila! Database created (even though server version is supposedly unsupported).

I Want Answers
  • 371
  • 3
  • 15