1. Sql Express Version
2. Sql Express Version Numbers
3. Sql Express Version 655 2
4. Sql Express Version 655 Free
5. Sql Server 2008 Express Version 655
6. Sql Express Version 10

SQL Server 2017 Express LocalDB. This version allows you to embed SQL Server Express into applications with LocalDB. It is a lightweight version of the SQL Server Express edition which is a replacement of the deprecated SQL Server Compact. However, thanks to Paul Randal (@PaulRandal) and his Q&A article in TechNet we have the following list: SQL Server 7.0 databases have version number 515 SQL Server 2000 databases have version. The v11.0 and MSSQLLocalDB instances are automatic Microsoft SQL Server Express LocalDB instances and come with installation of Microsoft SQL Server Express LocalDB. Depending on which version of Microsoft SQL Server Express LocalDB is installed on the machine, the different automatic LocalDB instance will appear.

I've manually attached the data and log files I received from a client to a SQL Server 2005 Express SP3 database. During the upgrade to SP4, I get the following error:

The database 'MyDatabase' cannot be opened because it is version 622. This server support version 612 and earlier. A downgrade path is not supported.

Does anyone know what database version 622 is and how I can install it? This database is from a Canadian customer so maybe it comes from an international version of SQL Server. I really wish there was a reference for the database versions so I knew what 622 is. Much Googling resulted in much frustration and no answers.

Adding some more information. The original database was corrupt. I was only able to restore it using a backup. The data files were a little newer (2 days) so we were seeing if we could use those as well.

Upgraded from SQL Server 2005 Express to SQL Server 2008 Express successfully while the corrupt database was attached. SELECT @@VERSION reports Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86). I ran sp_resetstatus, SET EMERGENCY and DBCC CHECKDB and received the following:

Msg 946, Level 14, State 1, Line 1
Cannot open database 'MyDatabase' version 622. Upgrade the database to the latest version.

Jon Seigel

3 Answers

622 is an internal intermediate version, never released. How come you have an 622 version DB? The explanation is simple actually: an aborted upgrade. Look at the sequence Aaron posted:

If the last step above crashes, your database is a version 622 now (each step commits). This version can only be attached to a SQL Server 2008 (or newer) to continue and finish the upgrade. It seems to me you had a SQL Server 2005 DB (v. 611) you attached to a SQL Server 2008 or higher, it started to upgrade but the upgrade failed at step 622->625 and now you're trying to attach it back to the SQL 2005 instance. It can't be re-attached, your only chance is to try to move forward. If the upgrade continue to fail, you will have to start again from an original SQL 2005 database (a copy of the files, a backup...).

Why would a database upgrade fail? Same reason any operation can fail: CTRL-C, power outage, corrupted original database, hardware problems, bugs in the product. Knowing what the upgrade step 622-625 does, my moneys are on a corrupted source DB. Recovering from a failed upgrade is a bit more tricky. As usual, having a good, tested, backup and restore strategy pays off.

Remus RusanuRemus Rusanu

622 is quite likely a very early beta or unreleased interim build of SQL Server 2008. Here is why I believe this is true. I have the highest possible build of SQL Server 2005 SP4:

That is 2005 + SP4 + CU3 + QFE from Security Bulletin MS12-070.

When I back the database up from 2005 SP4, and restore it on the very first RTM build of 2008:

I get the following database version messages during the restore:

Converting database 'x' from version 611 to the current version 655.
Database 'x' running the upgrade step from version 611 to version 621.
Database 'x' running the upgrade step from version 621 to version 622.
Database 'x' running the upgrade step from version 622 to version 625.
Database 'x' running the upgrade step from version 625 to version 626.
... 25 steps removed ...
Database 'x' running the upgrade step from version 651 to version 652.
Database 'x' running the upgrade step from version 652 to version 653.
Database 'x' running the upgrade step from version 653 to version 654.
Database 'x' running the upgrade step from version 654 to version 655.

You'll notice that 622 is the second of many, many steps on the path between any 2005 build and the very first official, public build of 2008. Since there are no CTPs or interim builds at the end of a release cycle, this leads me to believe that this was a very early build in the beginning of the 2008 release cycle.

What is much more mysterious is how you have an instance of SQL Server 2008 that thinks it is version 612 (which, as Remus rightly reminded us, is 2005 with the vardecimal option enabled), while @@VERSION - at least according to the question - returns 10.0.1600.22 (which is 2008 RTM). I suspect you are attempting the restore and running SELECT @@VERSION; on two different servers.

I would suggest you apply Service Pack 3 and Cumulative Update 14, and then try restoring your database to the 2008 server again. This should bring your database version up to 655 (or 662/663 if you enable 15K partition support), and at that point you should be able to restore your database with the 622 version no problem (as long as it didn't become corrupt during some botched upgrade, as Remus suggested).

Where do you get your builds of SQL Server? And why are you running x86? It's 2014. Is the underlying operating system really 32-bit?

Aaron Bertrand

Sql Express Version

♦

Sql Express Version Numbers

Aaron Bertrand

Simply put, your database comes from a more recent version of SQL Server then you are trying to attach it to and SQL Server does not support this. You can only attach databases to the same or newer versions of SQL Server than you got it from.

If you simply need to access the database and it isn't larger than 10GB, you can download SQL Server Express and attach the database to this. Note, this will upgrade the database to that version, so I would recommend making a backup of those files. IF your database is larger than 10GB, you will need SQL Server Standard, Enterprise, or Developer to attach it to.

Mike FalMike Fal

Not the answer you're looking for? Browse other questions tagged sql-serverrestore or ask your own question.

Microsoft SQL Server is an enterprise quality database management system that's usually hosted by a server and can scale across multiple servers and locations.

For local PC, small databases, and less critical situations, Microsoft offers a limited version of SQL Server called SQL Server Express. SQL Server Express can be downloaded for free and installed on your local PC. This is helpful for:

• Deploying desktop Windows solutions that use SQL Server databases to users who don't own SQL Server
• Deploying lightweight web applications that use SQL Server databases
• Developers wanting to create and test applications with a SQL Server database on their own, rather than a database hosted on a server

There are many editions of the full version of SQL Server with Enterprise, Standard and Web being the most common. Here are some of the major differences of the 2017 version compared to the 2016 and 2017 Express editions:

Enterprise	Standard	Web	2017 Express	2016 Express
Maximum Database Size	524 PB	524 PB	524 PB	10 GB	10 GB
Compute Capacity	OS Max	4 sockets or 24 cores	4 sockets or 16 cores	1 socket or 4 cores	1 socket or 4 cores
Maximum Memory	OS Max	128 GB	64 GB	1.4 GB	1.4 GB
Database Mirroring
Smart Backups, Encrypted Backups
SQL Profiler

The most critical issue is the maximum database size. The other differences are related to performance and maintenance.

For more details, visit Microsoft's SQL Server 2017 Comparison of Editions including Enterprise vs. Express and SQL Server 2016 editions and features.

Note: SQL Server Express cannot be installed on a compressed drive. It only supports standard, non-compressed drives.

Many versions of Microsoft SQL Server Express and service packs were released over the years. Here's a summary by Major Version:

Major Version	Service Packs
2017	None
2016	SP1 and SP2
2014	SP1 and SP2
2012	SP1, SP2, and SP3
2008	R2 RTM, R2 SP1, and R2 SP2
2005	SP1, SP2, SP3 and SP4

Note: SQL Server 2017 and later versions will no longer receive Service Packs, only Cumulative Updates and Critical Updates. For more details, visit Microsoft's SQL Server Service Packs are discontinued starting from SQL Server 2017.

Microsoft will no longer release security updates for SQL Server 2008/2008 R2. For more information, visit SQL Server 2008 and SQL Server 2008 R2 End Support.

Since organizations usually upgrade SQL Server less often than operating systems, an older version may be used for quite some time, especially if the application doesn't use the features added to the new versions.

• If starting from scratch, choose the newest version that supports all the operating systems you're targeting.
• If you are developing and need to eventually deploy to an actual version of SQL Server, you should use a SQL Server Express version that matches that version or an older version to avoid introducing features that don't exist on your SQL Server.

Here are the Microsoft SQL Express versions, when they were released, and the Operating Systems they explicitly support. The older versions generally work on newer operating systems but is not officially stated on Microsoft's web pages. The 2005 versions have a warning message when they are installed on Windows 8.x or later.

Links are also provided for downloading your own free copy of SQL Server Express and the related SQL Server Management Studio when it's not included in the main download.

Sql Express Version 655 2

SQL Server Express Version

2017

2016 SP1

2016

2014 SP2

2014 SP1

2014

2012 SP3

2012 SP2

2012 SP1

2012

2008 R2 SP2

2008 R2 SP1

2008 R2 RTM

2008

2005 SP4

2005 SP3

2005 SP2

2005 SP1

2005

Download Link

Download

Download

N/A

Download

Download

Download

Download

Download

Download

Download

Download

Download

Download

Download

Download

Download

Download

No Longer Available

Download

Published Date

2017-Oct-2

2016-Nov-11

2016-May-31

2016-Jul-11

2015-May-14

2014-Jun-25

2015-Nov-21

2014-Oct-23

2012-Nov-9

2012-May-14

2013-Jul-26

2011-Jul-12

2010-Apr-16

2009-Feb-8

2010-Dec-17

2008-Dec-15

2007-Feb-18

2006-Nov-9

2005-Nov-7

Includes SQL Server Management Studio

See Download

Download

Download

No Longer Available

Download

Download

Download

Download

Hardware and Software Requirements

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Details

Windows Desktop O/S

2017

2016 SP1

2016

2014 SP2

2014 SP1

2014

2012 SP3

2012 SP2

2012 SP1

2012

2008 R2 SP2

2008 R2 SP1

2008 R2 RTM

2008

2005 SP4

2005 SP3

2005 SP2

2005 SP1

2005

Windows 10

Windows 8.1

*

*

*

*

*

*

*

*

*

Windows 8

*

*

*

*

*

*

*

*

Windows 7 SP1

*

*

*

*

*

*

*

*

*

Windows 7

*

*

*

Windows Vista SP2

*

*

*

*

*

Windows Vista SP1

*

*

*

*

*

Windows Vista

*

Windows XP SP3

*

*

*

*

*

Windows XP SP2

Windows 2000 SP4

Windows Server

2017

2016 SP1

2016

2014 SP2

2014 SP1

2014

2012 SP3

2012 SP2

2012 SP1

2012

2008 R2 SP2

2008 R2 SP1

2008 R2 RTM

2008

2005 SP4

2005 SP3

2005 SP2

2005 SP1

2005

Windows Server 2003

Windows Server 2003 SP1

Windows Server 2003 SP2

*

*

*

*

Windows Server 2003 R2 SP2

*

*

*

*

Windows Server 2008

*

*

*

Windows Server 2008 SP2

*

*

*

*

*

*

Windows Server 2008 R2

*

*

*

Windows Server 2008 R2 SP1

*

*

*

*

*

*

*

*

Windows Server 2012

*

*

*

*

*

*

*

*

Windows Server 2012 R2

*

*

*

*

*

*

*

*

*

Windows Server 2016

*

*

*

*

*

*

*

*

*

Sql Express Version 655 Free

* not explicitly supported, but functional

Once you start creating databases in SQL Server Express, don't forget that you still need to backup your databases. Sure, SQL Server databases as self monitoring and you don't need to run periodic compacts like you do to keep Microsoft Access databases healthy, but backups remain important for archival and disaster recovery reasons. SQL Server can't stop someone from entering bad data or accidentally deleting all your records. Transaction logs can help recover data, but if there are lots of transactions, that may be difficult to accomplish.

Sql Server 2008 Express Version 655

Here's our whitepaper to Automate the Backup of Your Microsoft SQL Server Express Databases

We have a wide range of other papers and related SQL Server resources on the left border.

Sql Express Version 10

Topics include SQL Express on the Windows desktop, upsizing Access databases to SQL Server, SQL Server on the Azure Cloud, and other tips and techniques.

If you need help with SQL Server application development using Microsoft Visual Studio and related technologies, please contact us.