What is the version 869 of sql server ?
Question
Wednesday, April 18, 2018 12:42 AM | 1 vote
I use VS 2017 with sql server 2017 (localDB)
When I added data in another PC using my app and then copied the MDF and LDF files and tried to added them to new project BUT I got this error:
cannot be opened because it is version 869. This server supports version 852 and earlier. A downgrade path is not supported.
and this:
A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
So what do you think the problem is ?
Thanks.
All replies (8)
Wednesday, April 18, 2018 1:13 AM âś…Answered
You can't mount file that is created by SQL server 2017 with SQL 2016.
Wednesday, April 18, 2018 1:19 AM
**Thanks for your reply, **
I know that, I use just sql 2017 ! notice the version 852 is sql 2017
But the strange thing that version 869 undocumented !
Wednesday, April 18, 2018 1:34 AM | 1 vote
I mean, judge you the error message, the SQL server you try to mount MDF file to is SQL2016.
Try run "select @@version" as in the article and see what it says?
Wednesday, April 18, 2018 1:49 AM | 1 vote
Yes Yes, I was wrong !
I just thought that with VS 2017 comes SQL 2017 local DB by default !!
But in fact it is SQL 2016 !!
When I run my app in another pc I installed the sql localDB 2017 and it works perfectly!
THAT what let me become lost and to think that with VS 2017 comes SQL 2017 !
It seems sql server localDB 2017 NOT JUST support SQL 2016 it also modified the MDF file to become 869 version (SQl server localDB 2017) .
**But the question now : **
Why VS 2017 Not allow me to use this DB, I already installed SQL server 2017 configuration manger and even SQL server 2017 management tools!!?
Wednesday, April 18, 2018 10:18 AM
Assuming you installed both (or you won't have this confusion), try look at the connection string and see if there's anything related to version?
I'm no expert in LocalDB, so you're advised to ask the others to help, probably make a new question in SQL server forums.
Thursday, April 19, 2018 9:06 AM
Hi KeNaNo,
Thank you for posting here.
According to your question is more relayed to Sql Server, I will move it to Getting started with SQL Server forum for suitable support.
The Visual C# forum discuss and ask questions about the C# programming language, IDE, libraries, samples, and tools.
Best Regards,
Wendy
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Tuesday, July 30, 2019 8:39 PM
I'm running down the rabbit hole with this one. Mounting a newer database version of SQL on an older version of SQL. There is white paper from Microsoft and it points to "Permissions", not so much as "version".
/en-us/sql/database-engine/configure-windows/sql-server-express-localdb?view=sql-server-2017
"An instance of SQL Server 2016 ExpressLocalDB is an instance created by a user for their use. Any user on the computer can create a database using an instance of LocalDB, store files under their user profile, and run the process under their credentials. By default, access to the instance of LocalDB is limited to its owner. The data contained in the LocalDB is protected by file system access to the database files. If user database files are stored in a shared location, the database can be opened by anyone with file system access to that location by using an instance of LocalDB that they own. If the database files are in a protected location, such as the users data folder, only that user, and any administrators with access to that folder, can open the database. The LocalDB files can only be opened by one instance of LocalDB at a time."
So, I'm stuck in a similar rabbit hole. I have an .mdf from a friend and it simply won't mount - I get the same error 869 won't mount the 852 from Visual Studio. If you look closely, there is an msi in the link above. The LocalDB seems much like the older MDAC/MSDE distributions of SQL Server. One possible solution is to get whatever the latest msi offers for setting up the localdb on your machine and try again to mount the database.
In 2008 there was a method to pull the headeronly first and then load the backup file from a newer version (Labelonly, filelistonly) https://www.mssqltips.com/sqlservertutorial/105/how-to-get-the-contents-of-a-sql-server-backup-file/ The article is a decade old. It may still work.
R, J
Wednesday, July 31, 2019 6:13 AM
I get the same error 869 won't mount the 852 from Visual Studio
As already clearly stated in this thread, you can not attach a database for a newer Version to an older one; simply impossible and there is no working workaround or hack to do so.
Olaf Helper