Failure attaching SQL Server 2008 database to SQL Server 2005

1
votes

I developed an application in ASP.net 4.0 in visual studio 2010, connected with a SQL Server 2008 database. I copied my ASP.net application to a webserver IIS 6.0 with a SQL Server 2005 EXPRESS, OS Windows 2003 werver. When I try to browse my website I get the following error:

The database 'C:\TELEFOON\TELEFOON\APP_DATA\ASPNETDB.MDF' cannot be opened because it is version 655. This server supports version 611 and earlier. A downgrade path is not supported.

Could not open new database 'C:\TELEFOON\TELEFOON\APP_DATA\ASPNETDB.MDF'. CREATE DATABASE is aborted. An attempt to attach an auto-named database for file C:\Telefoon\Telefoon\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

I do understand the problem but is there a solution?

2
asp.netsql-server

2 Answers

6
votes

Sounds like you created the database on SQL Server 2008 R2, and are trying to open it on SQL Server 2008 (or SQL Server 2005? I forget internal database version numbers). You can't go backwards like this; you'll need to either install SQL Server 2008 R2 to restore the database directly, or you'll need to create an empty database and copy the table/structure using the SSMS wizards (like import/export data, which DOES work between versions in spite of O.D's comments to the contrary, or the generate scripts option) or 3rd party tools. I blogged about some 3rd party tools here:

http://bertrandaaron.wordpress.com/2012/04/20/re-blog-the-cost-of-reinventing-the-wheel/

This comment was more about the 2008 R2 -> 2008 problem:

Every time this happens I curse Microsoft for their absolutely moronic decision to name a full release of SQL Server "R2" - I blogged about this here, since every day there seems to be confusion that 2008 and 2008 R2 are the "same release" or that 2008 R2 is just a service pack:

https://sqlblog.org/2011/02/09/is-sql-server-2008-r2-a-full-release-of-sql-server

1
votes

Try the following it may help:

  • Select your database in the SSMS Wizard
  • right-click then selectTasks and Generate Scripts.
  • enable all options in the dialogbox including script data and "Script for SQL Server 2005".
  • Try to run the scripts on your SQL Server 2005.

If this doesnt help i can recommend you OmegaSync