October 5, 2013 at 11:13 am
Does anyone know of a way to restore a backup from SQLExpress to SQL 2008 R2? I was sent a backup and can't use it without getting it on SQL 2008 R2. Keeps saying I have to restore to SQLEXpress.
Thanks,
:w00t:
October 5, 2013 at 11:22 am
There's nothing special about a backup made on SQL Express, a backup taken from there can be restored to any edition of SQL of that version or lower.
What's the exact error message you're getting?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 5, 2013 at 1:01 pm
It said:
Restore failed for Server 'JIM-PC'. (Microsoft.SqlServer.SmoExtended)
Additional information:
System.Data.SqlClient.SqlError: The database was backed up on a server running version
10.50.4000. 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)
That to me appears that it can't restore SQLExpress backup to SQL 2008 R2
Jim:w00t:
October 5, 2013 at 1:59 pm
Nothing to do with SQL Express.
You have a SQL 2008 R2 backup that you're trying to restore to a SQL 2008 instance (not R2). They're two different versions and you can never restore down-version. You can restore up-version or between editions on the same version, but not down-version.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 5, 2013 at 3:49 pm
Thank you thank you thank you. I would never have figured that one out. I was told the back up was SQLExpress so I assumed that was the reason. I now see the version is a higher level on the backup than on my server.
Thanks again.
😀
October 5, 2013 at 4:14 pm
The only time the edition matters (Enterprise, Standard, Express, etc) is when the backup contains persistent Enterprise-only features like compression or partitioning. Only when that is the case can the backup not be restored to a different edition.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 6, 2013 at 12:14 pm
Just so you know, I went through hell getting R2 installed. It wouldn't upgrade from 2008 to 2008 R2 something about features not upgradable.
I then tried to remove all of 2008 and reinstall R2 but it said I had to give it an 'instance' which after two tries I did and it installed but apparently 2008 was not gone. When I tried to log on it kept going to the older version. Then I had to find out how to put the instance on the logon and finally got that working on the management studio but still can't get the logon to work through my VB code.
Anyway, SQL seems very difficult to work with. Not intuitive like most MS products. The defaults on the install didn't all work either especially since I couldn't get rid of the older version. I really didn't want multiple instances on my notebook but at least now I can work on the tables and the database, now if I could just logon with my VB Code I could actually do some work after loosing 3 days.
Thanks for all your help. I really appreciate it.
Jim
:-D:-)
October 6, 2013 at 12:18 pm
JimReid (10/6/2013)
Anyway, SQL seems very difficult to work with
Bear in mind that SQL is a server product, it's more like Exchange or Lync than Office or Visual Studio.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply