Connecting VS 2010 Ultimate to Sql server 2012

Question

0.00/5 (No votes)

See more:

Hi,

I am not able to connect sql server 2012 database with visual studio 2010 ultimate version. I have installed VS 2010 service pack 1 while installing sql server 2012. I am getting below error:

"The database C:/USERS/SACHIN/DOCUMENTS/First_Database.mdf can not be opened because it is version 706. This server supports version 655 and earlier. A downgrade path is not supported. Could not open new database C:/USERS/SACHIN/DOCUMENTS/First_Database.mdf.CREATE DATABASE is aborted. An attempt to attach an auto-named database for file C:/USERS/SACHIN/DOCUMENTS/First_Database.mdf failed. A database with the same name exists or specified file can not be opened, or it is located on UNC share."

Can you please let me know the reason for the error and how to resolve it?

Posted 24-May-13 15:57pm

Member 9166990

Updated 24-May-13 15:58pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

_Amy · Answer 1 · 2013-05-24T19:12:00

Solution 1

This is because your database is from SQL Server 2012. The only way to resolve this as I found is to Generate Script from SQL Server 2012 then run it in SQL Server 2008 R2.

--Amit

Posted 24-May-13 19:12pm

_Amy