I have a problem regarding a SQL Server database.
The error message is
Cannot be opened because it is version 852. This server supports version 782 and earlier. A downgrade path is not supported.
I tried everything, updating via Visual Studio 2015, downloading SQL Server 2016, installing SSMS, but nothing changed the server's version.
I need to somehow change the server's version so it will attach the the database successfully.
Please help!
You are attempting to attach SQL Server 2016 database files to SQL Server 2014. This is not supported.
Your only solution is to upgrade SQL Server from 2014 to 2016. Note, this is the database engine, not management studio.
Here is a list of all SQL Server internal database version numbers: http://sqlserverbuilds.blogspot.com/2014/01/sql-server-internal-database-versions.html
Related
We are currently using Primavera P6 Professional R8.3.2 with SQL Server 2008 R2. We are going to upgrade the SQL Server version from 2008 R2 to either 2014 or 2016 version. Could you please confirm that there are any compatibility issues between Primavera R8.3.2 and SQL Server 2014 or SQL Server 2016?
Edit:
We are going to migrate upgrade Windows Server 2008 R2 to Windows Server 2016. SQL Server 2014 and SQL Server 2016 are only supported in Windows Server 2016. Primavera web application is currently running in Apache/Weblogic OEL5.7 Server. We are going to upgrade Apache/Weblogic OEL5.7 Server to Linux 6.10 and 7.5(OEL) Server.
I have checked the tested configurations Excel file for compatibility issues. I am able to find the specified new Windows Server details and SQL Server details in the newer version (17. 7) of Primavera Excel file. But I am not able to find the Primavera web application's compatibility with new Linux 6.10 and 7.5(OEL) Server in the tested configurations Excel file. Could you please confirm the Primavera web application's compatibility with new Linux 6.10 and 7.5(OEL) Server?
What you want to do is to search Oracle's P6 tested configuration document. For every release of P6, they produce an xls spreadsheet that lists what infrastructure they have tested the tool on.
Here's a link to Oracle's documentation library: https://docs.oracle.com/en/industries/construction-engineering/primavera-p6-eppm/index.html where you can get the xls file.
PS: Now the xls file has been renamed "client system requirements" - search that or "tested configurations".
EDIT:
I'm not sure I can help you. The tested configurations doc indicate what infrastructure is supported. I would contact Oracle Support directly to get confirmation.
I have .mdf files created using SQL SERVER management studio in another computer and wish to attach the same to SQL SERVER 2008 EXPRESS in another computer. How should I do so?
I tried this method :How to: Attach a Database File to SQL Server Express
but then it shows an error that the database cannot be created due to compatibility issues.
Msg 948: The database xyz cannot be opened because it is version 706.
This server supports version 655 and earlier. A downward path is not
supported..
....
This basically means your SQL versions don't match. For example, if you backup a database on SQL 2012, you can't restore it to 2008. In your case Version 706 is a database file from Sql Server 2012 and Version 663 is a database file from Sql Server 2008R2 (with some SP).
You can either install SQL Express 2012 to attach the MDF, or if you can't do that, you would have to script out your schema and data and create the DB from scratch.. Unfortunately there's no way to 'downgrade' and MDF back to an older version of SQL.
The message is very clear:
The database MDF file is version 706. Your server understands version 655 . Which means, despite to your claim to the contrary, that you are connected to a SQL Server 2008.
Install a SQL Server 2012, connect to it, and attach your database.
Please pay attention during the installation process to the instance name you choose and make sure you connect to that instance.
You can also check now what instances you have installed, look at what services you have on your system.
SELECT ##VERSION AS 'SQL Server Version'
I have a .bak file that I am restoring but SSMS gives an error that is
"System.Data.SqlClient.SqlError: The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.1600. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. (Microsoft.SqlServer.Smo)"
I have updated SSMS, now its version is 10.50.4000. But the problem is still the same.
You may not restore a backup of a higher version of SQL to a lower version of SQL.
Have a look at sql server builds.
10.50.1600 is SQL Server 2008 R2 while 10.00.1600 is SQL Server 2008.
Updating SSMS is not going to work, as it is only a Client Tool, and not the Server itself.
You need to upgrade the Server engine in order for the upgrade to work.
To see this is true, you may open your newly upgraded SSMS and login to the server where you want to restore your backup. In the tree you will see the Server's version in a parenthesis next to the Server's name. You will notice that though you upgrader SSMS, the Server's version remains the same.
I have SQL Server 2012 and I'm trying to attach a db which was previously used with SQL Server 2012, surprisingly I'm getting the following error:
The database 'DatabaseName' cannot be opened because it is version
706. This server supports version 622 and earlier. A downgrade path is not supported.
I don't really understand how this could happen since like I said it was used with same 2012 version. What am I doing wrong? How can I make it work? Please explain in detail how this can be resolved.
Thank you!!
The error sounds like the server you are trying to attach the database to is not SQL Server 2012. This may be the version of Management Studio / Management Studio Express you're using, but I suspect SELECT ##VERSION; will tell you something different. It may just be a connection string mixup if you have multiple instances of SQL Server installed, otherwise you should download and install SQL Server 2012 Express from here.
#source
It sounds like you had the following configuration and source databases:
SQL Server 2008 SP3 (ver 10.0...) - database engine
SQL Server Management Studio 2012 (ver 11.0...) - management tools
a database that was created with SQL Server 2012 (version 706)
As mentioned you could install SSMS for SQL Server 2008 (after you uninstall SSMS for SQL Server 2012). Then you would have to script your database for that version and re-run the script via 'Tasks>Script...', remembering to set the target server version as shown below.
After scripting you can then use the import/export wizard to export and then inport the data into the new (downgraded database), assuming the database had no 2012-only datatypes (such as sequences).
Another consideration is database compatibility level as shown below. You can have a SQL Server 2012 instance which hosts databases with various compatibility levels.
Using SELECT ##VERSION works very well for me. Your Database Engine is connected to a 2008 DB which certainly doesn't allow you to attach. Once I change my Database Engine to connect to 2012 DB, it works for me.
Check your Database Engine connection. You can be working on 2012 Management Studio yet connecting to 2008 DB. This is what happened to me and I have solved it use SELECT ##VERSION.
When I want to attach database, an error occurs:
The database 'Almizan' cannot be opened because it is version 661.
This server supports version 655 and earlier. A downgrade path is not supported.
Could not open new database 'Almizan'. CREATE DATABASE is aborted.
(.Net SqlClient Data Provider)
Help me to attach this database.
Install SQL Server 2008 EXPRESS R2. There is a bug in the Web Platform Installer and it still thinks EXPRESS R1 is the latest version.
SQL Server 2008 databases are version 655. SQL Server 2008 R2 databases are 661. You are trying to attach an 2008 R2 database (v. 661) to an 2008 instance and this is not supported. Once the database has been upgraded to an 2008 R2 version, it cannot be downgraded. You'll have to either upgrade your 2008 SP2 instance to R2, or you have to copy out the data in that database into an 2008 database (eg using the data migration wizard, or something equivalent).
The message is misleading, to say the least, it says 662 because SQL Server 2008 SP2 does support 662 as a database version, this is when 15000 partitions are enabled in the database, see Support for 15000 Partitions.docx. Enabling the support bumps the DB version to 662, disabling it moves it back to 655. But SQL Server 2008 SP2 does not support 661 (the R2 version).
Think you need to upgrade the SQL Server 2008 instance (655) your trying to attach the database in, to SQL Server 2008 R2 (661), the version the database was actually created in.
See SQL Server: Attach incorrect version 661
The this answer on the MSDN seems to tell us the obvious
http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/01ed3b1c-6f29-4518-a3a4-e4e35decc05f/
When you attached the database to SQL Server 2008 to compress it the
database has automatically been upgraded from SQL 2005 to to SQL
Server 2008 from the disk structucture point of view. An internal
upgrade script has been run and has modified the on-disk structure of
the database to that new version. This can be seen at the version 655.
Once this has been done you can no longer attach the upgraded database
to a lower version of SQL Server, it will fail with the error you've
seen.
This has nothing to do with the compatiblity level of the database.
The compatabilty level only prevents the engine from using some of the
new features.
In order to get the database on SQL Server 2005 again you will need to
create the database freshly and export/import the data, for example by
using the Export/Import Wizard.
Ulrike - MSFT