This question already has answers here:
.mdf is too new (661) my database supports version 655
(5 answers)
How can I attach a database?
(3 answers)
Closed 9 years ago.
I'm using SQL Server. The version is as follow:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86) Apr 2 2010 15:53:02
Copyright (c) Microsoft Corporation Enterprise Edition
on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)
And when I try to attach Callbacks.mdf I get the following error:
Attach database failed for Server 'LT122580\SQLEXPRESS'.
(Microsoft.SqlServer.Smo)
The database 'Egor_Callback' 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 'Egor_Callback'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
I have no more available updates to SQL Server and I don't know what's causing this. Is it because I'm trying to attach it to SQL Server Express server? If so, How can I work around this problem without involving another server?
The big problem here is the misconception that SQL Server 2008 and SQL Server 2008 R2 are the same thing. They're not. 2008 R2 is not just a service pack to 2008, it is a completely different version, and the database structures are different.
Your database came from a SQL Server 2008 R2 instance (661) but you are trying to install it on 2008 (which only supports up to 655). In some ways this is like trying to take the carburetor from your '67 Corvette and trying to install it in your '64 Corvette. They're probably close, but not identical.
In order to use your 2008 R2 instance on your local Express instance, you will need to upgrade or add a new 2008 R2 instance of SQL Server Express. You could even install SQL Server 2012, which will be able to use databases from 2005, 2008, 2008 R2, and 2012.
Download SQL Server 2008 R2 Express
Download SQL Server 2012 Express
Related
When trying to attach a database file to:
Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) Sep 16 2010 19:43:16 <X64> (Build 7600: )
I get this error message:
The database cannot be opened because
it is version 661. This server
supports version 662 and earlier. A
downgrade path is not supported.
Any idea why? and how to solve it?
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).
To clarify, a database created under SQL Server 2008 R2 was being opened in an instance of SQL Server 2008 (the version prior to R2). The solution for me was to simply perform an upgrade installation of SQL Server 2008 R2. I can only speak for the Express edition, but it worked.
Oddly, though, the Web Platform Installer indicated that I had Express R2 installed. The better way to tell is to ask the database server itself:
SELECT ##VERSION
I am using Windows 7 32 bit OS and working on Microsoft SQL Server 2008, and when I open the configuration tool I got this error message.
Then I googled the error and got this below link.
http://www.microsoft.com/en-us/download/details.aspx?id=30437
Then I downloaded Microsoft® SQL Server 2008 R2 Service Pack 2
Then when I tried to install this application I got this error
How to solve this issue?? Any help appreciated.
In your question you write that you are using Microsoft SQL SERVER 2008but the download link is for Microsoft SQL Server 2008 R2, which is a different (newer) version. If you are indeed using the 2008 version and not 2008R2 what you want is the service pack for Microsoft SQL Server 2008: SQL Server 2008 Service Pack 3
I am getting the following error while trying to configure FileStream in SQL server 2012.
There was an unknown error applying the filestream settings. check the parameters are valid. (0x80041008)
I am configuring it using SQL server configuration manager.
Where as I am able to setup it for SQL server 2008 R2.
I had this same problem just yesterday.
In my case it was because I had a 64-bit Windows and a 32-Bit SQL Server.
You do not see the exact error, but if you try to do it with T-SQL, then the proper error comes up in SQL, telling you something about "WOW64" not supporting filestream.
I just uninstalled and installed the right bit version of SQL, and all worked 100% again.
In my case the problem I was running the SQL Server 2014 configuration manager. While this usually shouldn't cause problems, in my case it did. Configuring FILESTREAM using the SQL Server 2012 configuration manager worked.
If it still doesn't work, make sure you're up-to-date. SQL Server 2012 has received quite a lot of patches (SP2, SP3, and some updates).
TL;DR
I simply installed Service pack 2 (SP2) patch of SQL Server 2008 R2 and everything started working for me.
Read on if you want to know more. Configuration wise my box was all correct and the file stream feature should have been working on my default instance of SQL Server 2008 R2. Here are my box details:
Operating System: Windows 7 Ultitmate SP1 (64 Bit)
SQL Server Version: SQL Server 2008 R2 SP1
On SQL Server if I run this query select ##version it was returning following details:
Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
Whenever I opened SQL Server 2008 Configuration manager I will face this issue. Luckily I also had SQL Server 2014 installed on my machine. So I tried enabling File Stream feature from configuration manager GUI of SQL Server 2014 but it started giving error mentioned in current post.
I simply installed Service pack 2 (SP2) patch of SQL Server 2008 R2 and everything started working for me. SQL Server Configuration manager for 2008 R2 also works fine and I'm able to enable File Stream feature also without any trouble. SQL Server 2008 R2 SP2 can be downloaded from here.
I am using SSMS 2008 on an XP machine, trying to access a SQL Server 2012 database and get error messages indicating index out of bounds of array. What do I need to do to fix?
EDIT: (thanks #bluefeet ) : You can't install SSMS 2012 on Windows XP. See here: SQL Server 2012 Management Studio for Windows XP
Cause
The server you are connecting to is using SQL Server 2012. The error
is a result of incompatibilities with previous versions of SQL Server
Management Studio i.e. 2005, 2008, & 2008 R2.
Resolution
You will need to download SQL Server 2012 Management Studio to make
changes to your database. You can download it from the MSSQL Express
2012 website.
Source of Answer: You Receive Errors When Connecting to MSSQL 2012 Using MSSQL 2008 or 2008 R2 Management Studio.
This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
SQL Server Express 2008 Install Side-by-side w/ SQL 2005 Express Fails
I was wondering if you can have a SQL Express 2005 and a SQL Express 2008R2 instance installed on the same machine (OS: Windows 7).
I don't see why you can't? Someone at work told me you can't, but I have multiple SQL Express 2008 instances on my machine.
Yes; you can freely mix SQL Server 2005 and any flavor (R2 or not) of SQL Server 2008, and you can have multiple instances of both. 2005 and 2008 do not share any components, so they may as well be two completely independent products.
The only versions of SQL Server that can clash are 2008 with 2008 R2. Installing instances of 2008 and 2008 R2 on the same machine is not supported, as they have shared components that are different versions.
Yes, you can install multiple instances of SQL Server. Different versions, same versions...
You'll run out of resources (RAM, hard drive space) first....
Yes you can, I do on Windows 7. I installed SQL Server 2008 R2 last and installed it as named instance.